Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My website is hosted on*, which, at the time I purchased their service, seemed like a good enough host. I was (I hope) to be proved wrong.

Bascially, they are saying that

You need a Gold-package (which is the only account-type that offers a dedicated IP) to be able to have a private SSL.

Which is all fine and good. But, and here comes the fun part, they also say that

All other accounts have shared IP and SSL, meaning that if you use https, you might sometimes end up on the wrong website.

I call bullshit. Why? Two reasons:

  1. Compare my domain with SSL and without SSL (Notice the differens?)
  2. They refuse to uninstall SSL on my domain (I don't need it, but I sure as heck don't want shady stuff on my domain).

So, since I'm not the most versed in these matters (I'm a programmer, not a sysadmin), Im asking you, good folks:

Is any of this something any of you have encountered before, if so, how did you deal with it?
If not, how would you deal with it?

My reaction when I discovered this was, needless to say, "Let's get out of here, quick".

*Sorry, but I can only post two hyper-links. If any of you want, can you edit so the link to actually is a link (and also so, at the top of the post, website is [website])?

share|improve this question
up vote 4 down vote accepted

Multiple http websites can run on the same IP by pointing different domain names to it because the Webserver can look at the host headers and see which domain name was used. SSL requires a dedicated IP address because the host headers are encrypted and can not be checked in this manner.

Because domain names merely point to an IP address the SSL site on the machine will appear for all of the shared domains unless there is no SSL site setup on the IP at all. This will give a certificate error because the domain used will not match the domain of the certificate.

This is not a problem for the shared websites because it is clear that it is not their site, the cert error demonstrates that is being accessed by the wrong name, and most of all it will not be indexed under the shared domain names so the only way to access it is through an incorrect link or by manually typing in https://

share|improve this answer
What James said. And I don't see their explanation as bullshit. What they're saying is that, as a non-gold customer, you share an IP address with many (thousands of) other customers. Some or all of them are running https service on that address. In order not to have a listener on port 443 of the address to which your hostname resolves - which I presume is what you mean by "uninstall SSL on my domain" - you'd have to have a dedicated IP - which, as they point out, is the gold service. – MadHatter Sep 9 '11 at 9:40
This explains it! As I said before, I haven't really ever had anything to do with ssl, so I didn't have full understanding of how it worked. But now I do, thank you all! :) – Marcus Hasson Sep 9 '11 at 9:49
This is all true, but... at least on Apache a properly setup name-based virtualhost should display the correct content, even with SSL (I've used this myself). You'll get the "this is a bogus cert" warning, but if the client accepts the cert, the client will still send the Host header to the server, which Apache should use to select a VirtualHost block and show the correct content, not someone else's site. – DerfK Sep 9 '11 at 12:45
That is not a properly setup host but an incorrectly setup host. You are then using one person's certificate to sign someone else's content! – JamesRyan Sep 9 '11 at 12:55

this sounds like they are using cpanel

it also sounds like they setup a shared ssl certificate for another domain and your site is on the main shared IP, they cant uninstall this without breaking other sites on the server this is normal

if you dont want the risk of any shady business and ssl then you should get the dedicated IP with your own SSL, or a new hosting provider that doesnt do this. I'll agree there handling is not so transparent but this is not unusual to see in the wild

share|improve this answer
Well, it sure sounds like I should get another host. As far as I'm concerned, they're basically hijacking my domain. Oh, and yeah, they're using Cpanel. – Marcus Hasson Sep 9 '11 at 8:50
They are not hijacking anything. If you arn't paying for a dedicated IP address then you are accepting that there will be other services on the box. This is a common practice in a world where ipv4 addresses are scarce. – JamesRyan Sep 9 '11 at 9:18
It might not be hijacking per se, but it still feels kinda like they're totally screwing me. Especially since they provide no explanation or, well, anything really. Anyhow, thanks for the help, both of you! o/ – Marcus Hasson Sep 9 '11 at 9:37
they aint screwing you at all, its standard practice... – anthonysomerset Sep 9 '11 at 10:35

They are correct. You share the same IP with several other sites. So your site name resolves to this IP. This works great for HTTP, since HTTP inherently supports name-based virtual hosting. However, if other sites use other services that don't fully support name-based virtual hosting or that you choose not to support, people will be able to access those services through your domain name, because it resolves to the same IP as their names do.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.