Frequently Asked Questions

The NearlyFreeSpeech.NET FAQ (*)

General (*)

What's the most important thing to know about your service?

What's the most common mistake people make while signing up for NearlyFreeSpeech.NET?

Why do I have to enter my real name when creating a membership?

Can I beat your pricing if I get my own VPS?

How much does the average site really cost?

Do you provide email hosting services?

Is your service easy to use?

Do you provide DNS hosting services?

How many web sites can I host with a NearlyFreeSpeech.NET membership?

Do you register domain names?

How will I know if my account is about to run out of funds?

Why do you only offer prepaid service?

My web designer says I should use somebody else instead of you. What do you say?

Do you price-match your competitors?

How can you make money at these prices?

What is the minimum deposit?

Will you design my web site for me?

Do you offer collocation, dedicated servers, or VPS services?

What happens if I get slashdotted/reddited?

Are you about to pop up a "chat now with sales!" ad on me?

What if I want to set up a web site but don't have a domain name / don't want to fool with DNS?

How come your service isn't free?

What's the difference between bandwidth and storage?

Why doesn't your website look like other hosting provider sites?

Are your domain registration services intended for general-purpose usage?

What if my web site gets attacked?

Is your service only for controversial or extreme websites?

Should I set up my new small business website at NearlyFreeSpeech.NET?

Will you pre-approve my web site content or usage for compliance with your Terms and Conditions of Service?

How much will my site cost to host with you?

What kind of uptime can I expect with NearlyFreeSpeech.NET?

It depends. (Of course.) The short answer is: Not only don't we know, we can't know. The long answer uses the word "however" a lot.

Shared hosting has a well-earned reputation for volatility, due to the fact that you are sharing resources with other people and neither you nor we know from moment to moment what they or the visitors to their site are going to do. However, the most common causes of downtime for member sites are specific to the particular site affected (misconfigured DNS, an expired domain, runaway scripts, letting your prepaid account run out of funds, etc).

We find that when people ask us about uptime, they are expecting us to give them a magic number with a certain quantity of nines in it that represents what fraction of the time our service is available. However, our service is sufficiently varied and complex that offering such a number would be disingenuous, especially since we host a large number of sites and they don't all move in lock-step; one person's downtime might not affect someone else.

It would be very easy (and blatantly dishonest) for us to pick an arbitrary metric that would allow us to claim 100% uptime, or any number of nines we want. But, likewise, for any sufficiently large cluster of computers, something somewhere is always offline for maintenance, so we could probably make an argument for 0% uptime. (Though we won't.) Sites move back and forth, servers go up and down, and most of it happens without any visible effect. Even when a production server crashes (which does happen from time to time) it typically affects only a relatively small percentage over our members' sites, and usually only for a few minutes.

Our clustered approach does provide resiliency against many (but not all) types of hardware and load problems that cause downtimes at providers where your site is 100% dependent on the availability of a specific server. However, we do develop and maintain our own clustering software, so occasionally something incredibly weird may happen here that never would have or could have happened anywhere else. Such events are rare, but not without precedent.

Sites hosted at NearlyFreeSpeech.NET are probably slightly more likely to be "collateral damage" of a denial-of-service attack targeting some other controversial site hosted here than at other hosting companies that are less flexible in terms of hosted content. However, the flip side is that you are probably better protected against most such attacks due to our extensive experience with them, leading to (most likely) a very small net difference in the chance of being affected by that type of downtime.

All in all, our overall service availability is probably above average to very good when compared to other shared hosting providers. However, "overall availability" is meaningless to someone who's affected by something that doesn't affect everyone. Each person's view of our service availability can and will vary widely based on their personal experience as well as their personal criteria for what constitutes "availability."

We do monitor all of our systems and services continuously from multiple offsite locations and respond to problems detected as quickly as possible, 24x365.

Is this cloud computing?

Where are you located?

Do you offer telephone support?

Someone else uses your service and wants my help with it. How do I help them?

Should I use NearlyFreeSpeech.NET or a VPS?