Is my domain switched to the new server?
Enter your domain and the new server IP to see whether visitors already reach the new server, and whether that server is ready to serve the site.
What this tool checks
DNSPeek asks 20 public resolvers, from its own server, for the domain’s A (or AAAA) record and counts how many return the new IP. It also looks for leftover records of the other address family that would still send some visitors to the old server. At the same time it asks the new server directly for the home page over HTTP and HTTPS, with your domain as the host name, and reads its certificate. Private and reserved IP addresses are refused.
How to read the result
The percentage is the share of answering resolvers that already return the new IP. “Switching” means some do: the rest still hold the old answer until its TTL runs out. Below it, the server check tells you whether the new server answers for your domain, with which HTTP status, and whether browsers will trust its certificate.
What to check after a migration
Once the switch is done, check the certificate with the SSL checker, the redirects with the redirect checker and email with the MX lookup. Read how DNSPeek tracks propagation to get an email when it is done.
Frequently asked questions
When is a domain considered switched?
When at least 90% of the public resolvers that answer return the new IP, and at least half of them answered. That is the same rule the DNSPeek dashboard uses for its DNS propagation alert. If the new IP is a Cloudflare address, any Cloudflare address counts, because Cloudflare gives each region its own edge IP.
Why do I still see the old site after the switch?
Your own resolver, browser or operating system may still have the old answer cached until its TTL runs out. The resolvers in this check show how far the change has spread; flushing your local DNS cache or trying another network usually helps.
Why do resolvers show different Cloudflare IPs?
Cloudflare answers with the address of an edge server near each resolver (anycast), so resolvers in different regions get different Cloudflare IPs, such as 188.114.96.3, 104.21.66.63 or 172.67.201.135, for the same site. That is normal. When the IP you expect is a Cloudflare address, DNSPeek counts a resolver as matched when every address it returns belongs to Cloudflare’s published ranges, not only when it returns that exact IP.
I use Cloudflare proxy — how do I check my migration?
With the proxy on (orange cloud), public DNS shows only Cloudflare’s addresses and hides your origin server. When you change the origin IP inside Cloudflare, DNS does not change at all and Cloudflare applies the new origin within seconds, so a DNS check cannot show that switch. Check the new server directly instead: “Is my domain switched?” asks your new IP for the site, and a DNSPeek preview link with the new IP as the target shows the whole site from that server before you change anything in Cloudflare.
What does the server check do?
DNSPeek connects to the IP you entered and requests the home page over HTTP and HTTPS with your domain as the host name. That shows whether the new server is set up for the domain and whether its certificate covers it, even before DNS points there.
Can I get an email when the switch is done?
Yes. Create a free preview link for the domain and the new IP, then turn on “Alert me when DNS has propagated” in the link settings. DNSPeek checks every 5 minutes and emails you once.
Moving a site to a new server?
See the site on the new server before you change DNS: DNSPeek gives you one HTTPS preview link that works on any device and that you can share with your team or client. No hosts file, no VPN.
Create a free preview link