Hosting DNS Lookup

Check your domain's DNS zone at Hosting.com, GoDaddy, Hostinger and 11 more hosts, from their own nameservers: what's missing before a switch, and how long caches hold the old answers after.

The registry and each host's own nameservers, asked directly · Google and Cloudflare caches · no log kept

How to check your DNS at a host before switching nameservers

To check a host before you switch, ask its own nameservers: this page runs an authoritative DNS lookup there and compares each record with the live zone.

  1. Add the domain at the new host: nothing is copied when the nameservers change.
  2. Pick the host and check: a DNS comparison, record by record, with the line to add for each one missing.
  3. Switch the nameservers once the result says Ready to switch.
One domain, asked at ten servers of nine hostsgilat.com · recorded October 24, 2026

Holds the zone

  • GoDaddyits pairns55.domaincontrol.comNOERROR aathe zone's SOAThe zone

Says it has no zone

  • GoDaddyanother pairns21.domaincontrol.comREFUSEDno recordsNo zone
  • Hosting.comns1.stableserver.netREFUSEDno recordsNo zone
  • 20ins1.stackdns.comREFUSEDno recordsNo zone
  • SiteGroundns1.siteground.netREFUSEDno recordsNo zone
  • Namecheapdns1.registrar-servers.comREFUSEDno recordsNo zone
  • Hostingerns1.dns-parking.comNXDOMAINno aa, no SOANo zone

Answers with aa, holds no zone

  • Bluehostns1.bluehost.comNOERROR aacatch-all, SOA of com.Catch-all
  • HostGatora shared serverns2207.hostgator.comNOERROR aacatch-all, SOA of .Catch-all
  • ResellerClubresellerclub.mercury.orderbox-dns.comNOERROR aamade-up SOA, A 127.0.0.1Made up

aa + an SOA owned by the domain, naming a real host is a zone. Anything else is not.

Asked with dig +norec +tcp, the way this page asks. Only gilat.com's own GoDaddy pair holds its zone.
dig @ns1.stableserver.net example.com SOA +norec

The answer is in dig's header: the status and flags lines.

How to read the answer

  • flags: qr aa and an SOA for the domainA zone: the host holds the domain.
  • status: REFUSED · Hostinger's ns1/ns2: NXDOMAINNo zone yet: add the domain at the host first.
  • No answer, or a timeoutNot “no zone”: ask another of its servers.
Hosting DNS lookup of webcentral.in: live at Hosting.com, each record answering from its zone, the move column and cachesHosting DNS lookup of webcentral.in: live at Hosting.com, each record answering from its zone, the move column and cachesThe verdictWhere the domain stands at that host, and the next step.The comparisonEach record at the host beside the live answer, with a state chip.The registryWho the registry sends resolvers to, and for how long.The zone at the hostTen cells, one per record a move must carry.The cachesGoogle's and Cloudflare's copies, with the time left on each.
A check of webcentral.in, live at Hosting.com. Select a number to see what each part shows.

Hosting.com nameservers (and A2 Hosting, Stablepoint, Verpex…)

Hosting.com's nameservers are ns1.stableserver.net, ns2.stableserver.net, ns3.stableserver.net and ns4.stableserver.net, the same four for every hosting product. A2 Hosting accounts use them too: A2 became Hosting.com on 28 April 2025.

Its brands and resellers often show their own names, such as ns1–4.mysecurecloudhost.com or ns1–4.verpex.com, on the same four addresses, so the page recognises Hosting.com by address. Some older accounts use another set: use the one your account shows.

11 name sets, four addressesdig A · October 24, 2026
  • Hosting.comdocumentedns1–4.stableserver.net→ 13.248.158.180, 75.2.118.134, 76.223.26.245, 99.83.147.209
  • A2 Hostingnow Hosting.comns1–4.a2hosting.com→ 13.248.158.180, 75.2.118.134, 76.223.26.245, 99.83.147.209
  • Verpexns1–4.verpex.com→ 13.248.158.180, 75.2.118.134, 76.223.26.245, 99.83.147.209
  • Verpexdefault setns1–4.mysecurecloudhost.com→ 13.248.158.180, 75.2.118.134, 76.223.26.245, 99.83.147.209
  • Stablepointns1–4.stablepoint.com→ 13.248.158.180, 75.2.118.134, 76.223.26.245, 99.83.147.209
  • MochaHostns1–4.mochahost.com→ 13.248.158.180, 75.2.118.134, 76.223.26.245, 99.83.147.209
  • Doteasydns1/2/7/8/21.doteasy.com→ 13.248.158.180, 75.2.118.134, 76.223.26.245
  • Nimbus Hostingns1–3.nimbushosting.co.uk→ 13.248.158.180, 75.2.118.134, 76.223.26.245
  • DollarHostdns1 + dns2.dollarhost.com→ 13.248.158.180, 75.2.118.134
  • HostingRajans1 + ns2.hostingraja.com→ 13.248.158.180, 75.2.118.134
  • Melbourne ITns11 + ns12.melbourneit.com.au→ 13.248.158.180, 75.2.118.134
  1. 13.248.158.180ns1
  2. 75.2.118.134ns2
  3. 76.223.26.245ns3
  4. 99.83.147.209ns4

a79764cc55c0ac9c0AWS Global Accelerator · ns1 + ns3

abc65dd9a44b5332fAWS Global Accelerator · ns2 + ns4

“These are the same nameservers for every hosting product, and they are Anycast.”

Hosting.com KB, “Using Anycast DNS”, read October 24, 2026 · AS16509 (Amazon) · .net registry glue TTL 2 days
Green lines: the set Hosting.com (the former World Host Group) documents. The others are its brands' and resellers' sets, on the same four servers.

GoDaddy, Hostinger, Bluehost and the other major hosts' nameservers

Some hosts give every customer one set, such as SiteGround's ns1 and ns2.siteground.net; GoDaddy, Wix, OVHcloud and HostGator give each account or plan its own pair, Hostinger each site, and Squarespace uses six sets: the panel shows yours.

A reseller's branded names resolve to its platform's addresses, which is how the page tells whose servers they are.

White-label nameservers, recognised by addressdig A · October 24, 2026
  • ns1.serverbyt.neta reseller's own name35.197.225.59= ns1.stackdns.com20i
  • ns1.mochahost.comMochaHost: a hosting.com brand13.248.158.180= ns1.stableserver.netHosting.com
  • dns1.bigrock.inBigRock: its default set162.251.82.250one of ResellerClub's 16 addressesResellerClub
A reseller's own names prove nothing; the addresses they resolve to do.
Customer nameservers by host14 hosts · measured October 24, 2026
HostNameserversSetA domain it doesn't holdHow to change
Hosting.comns1–4.stableserver.netbrand sets: the same four addressesone shared setREFUSEDno recordsGuide (Hosting.com: how to change nameservers)
GoDaddynsNN.domaincontrol.coma pair per account, such as ns55 + ns56REFUSEDno recordsGuide (GoDaddy: how to change nameservers)
Hostingerns1 + ns2.dns-parking.compixel + byte.dns-parking.coma pair per site, such as pixel + byteper sitevia GlobalpingNXDOMAINon ns1/ns2; named pairs: REFUSEDGuide (Hostinger: how to change nameservers)
Bluehostns1 + ns2.bluehost.comone shared setvia GlobalpingNOERROR aacatch-all, SOA of com.Guide (Bluehost: how to change nameservers)
SiteGroundns1 + ns2.siteground.netone shared setREFUSEDno recordsGuide (SiteGround: how to change nameservers)
Namecheapdns1 + dns2.registrar-servers.comdns1 + dns2.namecheaphosting.comBasicDNS and hosting: one platformone shared setREFUSEDno recordsGuide (Namecheap: how to change nameservers)
HostGatornsNNNN / cnsNNN.hostgator.coma pair per serverNOERROR aashared servers: catch-allGuide (HostGator: how to change nameservers)
IONOSns1ZZZ.ui-dns.de / .biz / .org / .comfour names per domain; any numbered server answersany numbered serverREFUSEDno recordsGuide (IONOS: how to change nameservers)
OVHcloudnsNN + dnsNN.ovh.neta pair shares its numberREFUSEDno recordsGuide (OVHcloud: how to change nameservers)
DreamHostns1–3.dreamhost.comone shared setvia GlobalpingREFUSEDno recordsGuide (DreamHost: how to change nameservers)
Squarespacens01–04.squarespacedns.comnsa1–4 … nse1–4.squarespacedns.comsix sets; each refuses the others' zonesseveral setsREFUSEDno recordsGuide (Squarespace: how to change nameservers)
Wixns0–ns15.wixdns.neta pair per account, on one of two groupsREFUSEDno recordsGuide (Wix: how to change nameservers)
20ins1–4.stackdns.comresellers' own names: the same four addresseswhite labelREFUSEDno recordsGuide (20i: how to change nameservers)
ResellerClub<prefix>.mercury / .venus / .earth / .mars.orderbox-dns.comBigRock and resellers' names: the same 16 addresseswhite labelvia GlobalpingNOERROR aamade-up zone, A 127.0.0.1Guide (ResellerClub: how to change nameservers)
Each Guide link opens the host's own page on changing nameservers. A per-account host's zone answers only on its own pair or group.

Why your host's DNS and public DNS show different records

A host answers for every zone an account has added, even when the registry points elsewhere, so only the registry's delegation decides which copy the world uses.

Public resolvers keep each answer for its TTL, so for a while they can hand out an older copy than the zone holds: the result shows the time left on each.

Two copies of one domainmysecurecloudhost.com · recorded October 24, 2026

The .com registry sends resolvers for mysecurecloudhost.com to cass.ns.cloudflare.com and wesley.ns.cloudflare.com · NS TTL 2 days

What the world getsdelegatedthe live zone, through Cloudflare 1.1.1.1

NS · differs
cass.ns.cloudflare.comwesley.ns.cloudflare.com
A · differs
104.26.2.241104.26.3.241172.67.74.113
AAAA · differs
2606:4700:20::681a:2f12606:4700:20::681a:3f12606:4700:20::ac43:4a71
www · differs
NXDOMAIN
MX
0 mail2.mysecurecloudhost.com
TXT
v=spf1 a mx include:spf.mysecurecloudhost.com -allgoogle-site-verification=60zAOf…
_dmarc · differs
v=DMARC1; p=none; rua=mailto:… ruf=mailto:…v=DMARC1; p=none;
SOA
cass.ns.cloudflare.com. 2418131132

The zone at Hosting.comnot delegatedstill answering on ns1.stableserver.net

NS · differs
ns1.mysecurecloudhost.comns2.mysecurecloudhost.comns3.mysecurecloudhost.comns4.mysecurecloudhost.com
A · differs
35.246.3.36
AAAA · differs
none
www · differs
CNAME mysecurecloudhost.com
MX
0 mail2.mysecurecloudhost.com
TXT
v=spf1 a mx include:spf.mysecurecloudhost.com -allgoogle-site-verification=60zAOf…
_dmarc · differs
NXDOMAIN
SOA
ns1.mysecurecloudhost.com. 2026061001
Shaded rows differ. The SOA serials aren't compared: each host numbers its own zones.

How long a nameserver change takes

Up to the longer of the registry's NS TTL and the old zone's own NS TTL, counted from the change at the registry: two days for .com and .net.

Hosts quote their own ranges, such as Hosting.com's 15 minutes to 48 hours and 20i's 6 to 8 hours; keep the old host's zone answering until every cache has moved.

The registry's NS TTL, by TLD21 TLDs · measured October 24, 2026
  • .ru4 days
  • .com.net.uk2 days
  • .de.jp.es.pl.kr1 day
  • .tr.vn12 hours
  • .dev3 hours
  • .pt2 hours
  • .org.io.co.br.fr.id.au1 hour
  • .in15 minutes

What the hosts say

  • Hosting.com15 min – 48 hr
  • GoDaddyusually 1 hr, up to 48 hr
  • Hostingerup to 24 hr
  • Bluehost24–48 hr
  • HostGator24–48 hr
  • SiteGroundup to 72 hr
  • Namecheapup to 24 hr
  • IONOSup to 48 hr
  • OVHcloudup to 48 hr
  • Squarespaceup to 48 hr
  • Wixup to 48 hr
  • 20iusually 6–8 hr, up to 24 hr
  • ResellerClub24–48 hr
Bars: the NS TTL each TLD's own servers hand out, asked at two servers for two domains each. Chips: the range each host's help pages give.

What breaks in a move: MX, SPF, DMARC, www and verification TXT

Whatever the new host's zone lacks stops working the moment resolvers move to it: nothing is copied when the nameservers change.

Without MX, mail goes to the domain's own address and usually bounces (RFC 5321 §5.1); without SPF, its mail fails SPF, and Gmail has rejected more failing mail since November 2025.

Six records gilat.com's next host must carrylive at GoDaddy · recorded October 24, 2026
  • MXMail

    0 gilat-com.mail.protection.outlook.com.

    If it's missing: mail stops reaching Microsoft 365

  • TXTSPF

    v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com +9 more terms -all

    If it's missing: every sender gets SPF “none”

  • TXTDMARC

    v=DMARC1; p=none; rua=mailto:dmarc_agg@vali.email

    If it's missing: no DMARC policy, no reports

  • Awww

    192.124.249.6 · 192.124.249.114

    If it's missing: www.gilat.com stops resolving

  • TXTMicrosoft 365

    MS=ms45285377

    If it's missing: Microsoft's string is gone

  • TXTOther verification strings×2+2

    google-site-verification=e2qS6l…

    If it's missing: their strings are gone

Records from gilat.com's live zone at GoDaddy. DKIM keys sit under selector names a lookup can't list: copy them from the mail provider.

Per-account nameservers: GoDaddy, Hostinger, Wix, OVHcloud, HostGator

GoDaddy, Hostinger, Wix, Squarespace, OVHcloud and HostGator keep each zone on one assigned group of servers, and a server of another group answers REFUSED even for a zone the same host holds. IONOS gives each domain four numbered names, but any numbered server answers for it.

So the page asks the pair from the delegation, or the pair typed under the chips from the host's panel (GoDaddy: DNS → Nameservers); it never guesses one.

GoDaddy's pairs, one cell each38 pairs seen

In 4,000 random sites from the Tranco list · 140 of them use GoDaddy

  1. ns01: 3
  2. ns03: 5
  3. ns05: 2
  4. ns07: 2
  5. ns09: 3
  6. ns11: 1
  7. ns13: 4
  8. ns15: 4
  9. ns17: 1
  10. ns19: 1
  11. ns21: 2
  12. ns23: 4
  13. ns25: 2
  14. ns27: 1
  15. ns29: 7
  16. ns31: 6
  17. ns33: 1
  18. ns35: 4
  19. ns37: 0
  20. ns39: 4
  21. ns41: 4
  22. ns43: 2
  23. ns45: 2
  24. ns47: 6
  25. ns49: 6
  26. ns51: 7
  27. ns53: 3
  28. ns55: 5
  29. ns57: 1
  30. ns59: 1
  31. ns61: 0
  32. ns63: 6
  33. ns65: 5
  34. ns67: 3
  35. ns69: 2
  36. ns71: 4
  37. ns73: 1
  38. ns75: 2
  39. ns77: 3
  40. ns79: 0
  41. ns81: 4
  • ns55 + ns56 gilat.com's pair: NOERROR aa · 70 ms
  • ns21 + ns22 another pair: REFUSED
  • Bar: sites on that pair · dashed: not seen

HostGator

grandhyper.com → cns335 + cns336.hostgator.com

NOERROR aaits pair, with the zone

NOERROR aans2207 a shared server: a catch-all, SOA owned by .

“Using other name servers on our network won't work since your domain name's information is on the name servers provided.”

IONOS

usercentrics.com → ns1018 / 1093 / 1108 / 1112.ui-dns.*

NOERROR aans1010 · ns1127 any numbered server, not only its four

REFUSEDns-diy another group

“For security reasons, IONOS spreads the name server assignments across multiple name servers.”

OVHcloud

manceraparfums.com → ns111 + dns111.ovh.net

NOERROR aaits pair, with the zone

REFUSEDns200.anycast.me another group

“Two OVHcloud DNS servers are part of the same DNS server group if they share the same number.”
Asked live on October 24, 2026. Hosts with one shared set answer for any of their zones on any of their servers: Hosting.com, Namecheap, SiteGround, Bluehost, and DreamHost.

Hosting DNS questions

What are Hosting.com's nameservers?

Hosting.com's nameservers are ns1.stableserver.net, ns2.stableserver.net, ns3.stableserver.net and ns4.stableserver.net, the same four for every hosting product, on an anycast network. Brand and reseller sets such as ns1–4.mysecurecloudhost.com or ns1–4.verpex.com resolve to the same four addresses. Hosting.com notes that some older accounts use a different set, so check the nameservers shown in your account.

What are A2 Hosting's nameservers now?

A2 Hosting became Hosting.com on 28 April 2025, and its accounts use Hosting.com's set: ns1.stableserver.net to ns4.stableserver.net. Older domains may still point at ns1–4.a2hosting.com, which this page recognises as Hosting.com's servers by their addresses. Pick the A2 Hosting chip to check a domain's zone there before or after you change nameservers.

How do I check my DNS records before changing nameservers?

Add the domain to your account at the new host, then enter it above and pick the host. The page asks the host's own nameservers directly and compares each record with the live zone: missing MX, SPF, DMARC, www or verification records are listed with what would break and the zone-file line to add, so you can fix them before you switch.

Why does the host answer REFUSED for my domain?

REFUSED is how Hosting.com, GoDaddy, SiteGround, Namecheap and most other hosts say they hold no zone for a name. The domain hasn't been added to an account there yet, or it was added on another server group. Add it in your hosting panel, check again, and switch nameservers only once the zone is there.

Can a host have a zone for my domain without hosting it?

Yes. A host answers for any zone one of its accounts has added, whether the registry points there or not: some customers have added zones for google.com at Hosting.com and for bbc.co.uk at 20i. That's why this page reads the delegation first: a zone at a host is "ready, not live" until the registry points to it.

How long does a nameserver change take?

Up to the longer of the registry's NS TTL and the old zone's own NS TTL, counted from the change at the registry: two days for .com and .net. Many resolvers move much sooner. After a switch, this page shows the time left on Google's and Cloudflare's copies and the latest time every resolver has the new set.

Will my email stop working when I change nameservers?

Only if the new host's zone lacks your mail records. Nothing is copied when nameservers change, so MX, SPF, DKIM and DMARC records must be added at the new host first. Without MX, mail goes to the domain's own address instead of your mail provider and usually bounces. The readiness check lists missing MX, SPF and DMARC records with the line to add; copy DKIM keys from your mail provider.

What are GoDaddy's nameservers?

GoDaddy gives each account a pair of the form nsNN.domaincontrol.com, such as ns55 and ns56.domaincontrol.com, and a zone answers only on its own pair: another pair answers REFUSED. GoDaddy shows yours under DNS, then Nameservers. To check a zone at GoDaddy before a switch, pick GoDaddy above and enter that pair.

What are Hostinger's nameservers?

Hostinger gives each site its own pair on dns-parking.com: older sites use ns1 and ns2.dns-parking.com, newer ones named pairs such as pixel and byte, and a zone answers only on its own pair. Use the two hPanel shows for your site. They sit on Cloudflare's network, which our server can't connect to, so this page asks them through a Globalping probe from your browser.

Is this the same as a DNS propagation checker?

No. A propagation checker asks many public resolvers what they have cached. This page asks one host's own nameservers what its zone holds, compares that zone with the live one before you switch, and after a switch shows how long the big caches can keep the old answer. For the resolvers' view across the world, use the DNS propagation checker.

How is this different from NS Lookup?

NS Lookup checks the nameservers a domain is delegated to now: whether each one answers, its glue, DNSSEC and serials. This page asks a host you pick, delegated or not, whether it holds a zone for the domain and how that zone compares with the live one, which is what you need before and right after a move between hosts.

Missing something?Suggest a feature or a new tool