Almost always, this is DNS propagation and it fixes itself. Work down this list.
1. How long has it been?
If you changed your domain in the last hour, wait. Changes usually appear within minutes but can take up to 48 hours to be visible everywhere.
The reason: DNS answers are cached, and caches expire on their own schedule. Your customer in another town may be holding an old answer for a few more hours.
2. Try a device on a different network
Turn Wi-Fi off on your phone so it is on mobile data, and try again.
If it works on mobile data but not on your home or office Wi-Fi, that is a local cache. Your router or computer is holding the old answer. It will clear on its own, or you can restart the router to hurry it.
This is the most common cause of “it works for everyone but me”.
3. Check you typed it right
Obvious, but it happens. Try both with and without www.
4. Have you actually changed the nameservers?
If you brought an existing domain, the change has to be made at whoever the domain is registered with — not wherever your old website was hosted, if those are different companies.
Sign in to your registrar and confirm the nameservers match the two we gave you exactly. A single typo means it will never work, no matter how long you wait.
5. Is the domain still registered?
If it expired, everything stops. Check for renewal emails from your registrar — including in spam. An expired domain is recoverable, usually for a fee, but the clock matters.
If we registered the domain for you, this cannot be the problem; we renew them.
6. Is your site actually live?
Check your dashboard. If the site still says Ready to preview, it has not been published yet — the domain is pointing at us correctly and there is simply nothing there to serve.
7. “Not secure” or a certificate warning
This usually means the domain has just started pointing at us and the certificate has not finished being issued. It is normally sorted within an hour of the DNS resolving. See SSL and the padlock.
Still not working?
Get in touch and include:
- The domain name
- What you see — a blank page, an error, an old website, a certificate warning
- When you made the change
- Whether it works on mobile data
That last one saves the most time, because it tells us immediately whether the problem is your cache or our configuration.
What we can see from our side
We can check what your domain currently resolves to, whether the nameservers have taken effect, and whether the certificate has been issued. Usually we can tell you within a few minutes whether it is genuinely broken or just not finished propagating.