My domain isn't loading the right site

Applies to: All plans.

Your domain is loading an old, parked or wrong site because it is still pointed at a previous host, or your own device has cached the old answer. The fix is to confirm your domain points at Maxinodes, then clear the stale answer your browser or network is holding. Work through the checks below in order.

Symptoms

Your domain still shows your old website or your previous host's holding page.
You see a "parked", "coming soon" or registrar default page instead of your site.
The site loads correctly on one device or network but not another.
A colleague sees the new site while you still see the old one.

Common causes (most likely first)

Nameservers are not set to ours. The domain's DNS is still answered by your old host or registrar, so it serves the old site.
A stale A record points at the old server. Your nameservers may be ours (or your old provider's) but the root A record still holds the old IP address.
Your browser or device has cached the old answer. Your machine remembers the previous site or IP for a while.
The change is still propagating. DNS changes take time to reach everyone worldwide.
You edited DNS in the cPanel zone editor. On our platform the cPanel zone editor does not control live DNS, so nothing happened.

Quick fixes

1. Check your nameservers

Look up where your domain's DNS is answered. You can use any public "DNS checker" or "whois" website and search for your domain's NS (nameserver) records. They should read:

ns1.maxinodes.com
ns2.maxinodes.com

If they show your old host's nameservers instead, set ours at your registrar. See How to point your domain to Maxinodes (set your nameservers).

Result: Once the nameservers are ours and the change propagates, your domain's DNS is managed in your client area and serves your Maxinodes site.

2. Check the A record

If your nameservers are already ours, check the root A record. Open client area -> Domains -> My Domains, select the domain, and open its DNS management. The root record (host shown as @ or your bare domain) should be an A record to:

185.185.49.198

Set or correct it if it still holds an old value, and point www at the same place (an A record to 185.185.49.198, or a CNAME to your root domain). See How to manage DNS records in your client area.

Important: Customer websites are served over both IPv4 and IPv6 (dual-stack). When your domain uses our nameservers, the zone also contains AAAA records — check that the root and www AAAA records still point at our IPv6 address 2a00:7c80:0:286:c::10, and correct them if an old value was left behind.

3. Clear your own cache

If the records look correct but you still see the old site, your device is the problem. Try these in order:

Open the site in a private/incognito window, or a different browser.
Try a different network — for example, your phone on mobile data instead of Wi-Fi.
Hard-refresh the page (hold Shift and reload).
If it still sticks, restart your browser or your device to flush its DNS cache.

Result: If a private window or a different network shows the correct site, the records are fine and only your local cache was stale — it will clear on its own shortly.

4. Allow time to propagate

If you only just made a change, give it time. Propagation is usually minutes to a few hours, and up to 24–48 hours worldwide in the worst case, governed by the record's TTL. See How long does DNS propagation take?.

If that did not work

You changed records in cPanel and nothing happened. The cPanel zone editor does not control live DNS on our platform. Make all DNS changes in your client area instead.
The site loads but shows a security warning. AutoSSL needs a little time to issue a certificate once the domain points to us. See Free SSL (AutoSSL) and how to force HTTPS.
The domain does not load at all (not a wrong site, but an error or nothing). See My domain or DNS isn't resolving.
Still stuck after 48 hours. Contact support with your domain and what you changed, and we will check the zone from our side.