I am a webmaster for a local non-profit organization that has previously had its web host supplied to the organization by a third party. That party charges the organization for hosting but does not reveal any details at all, such as the bandwidth supplied or used. I'm thinking that the organization might be better off selecting its own web host, but I am a novice when it comes to selecting an appropriate host. Also, the non-profit's web address is currently owned by the third party. (I am a member of the non-profit who volunteers to be a webmaster.)

The organization is small and almost all of its bandwidth is used for outgoing web traffic. The storage requirement is well under 100 megabytes and my guesstimate of outgoing traffic would be 4 Gigabytes per month peak with much lower amount during some months.

Googleing for web hosts, I see quite a wide range of charges for a seemingly suitable amount of service, ranging from $12 per year (3iX) to $80 per year (Mailaka). The higher figure is less than half the charge that the non-profit currently pays.

While I understand the basics of web hosts, I don't know the details or pitfalls that may lurk.

Any advice to help me decide whether to switch hosts and how to select a new host?


************************************************************************
* ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in  <==
* ==> the body of an email & send 'em to: [EMAIL PROTECTED] <==
* Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name
* Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST
* Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L
* New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress
* Need more help? Send mail to: [EMAIL PROTECTED]
************************************************************************
* List archive at www.mail-archive.com/computerguys-l@listserv.aol.com/
* RSS at www.mail-archive.com/computerguys-l@listserv.aol.com/maillist.xml
* Messages bearing the header "X-No-Archive: yes" will not be archived
************************************************************************

Reply via email to