SOA Record Lookup
The SOA record holds administrative metadata for a domain's DNS zone, including the serial number. Look up any domain's SOA across 21 global servers to confirm every server has the same version of the zone.
Global DNS Propagation
 New York, USA Google | --- |
| Chicago, USA Gcore | --- |
| Los Angeles, USA Cloudflare | --- |
 Toronto, Canada CIRA | --- |
 Mexico City, MX OpenDNS | --- |
 London, UK Quad9 | --- |
 Frankfurt, Germany DNS.Watch | --- |
 Paris, France FDN | --- |
 Amsterdam, NL OpenNIC | --- |
 Moscow, Russia Yandex | --- |
 Singapore Singtel | --- |
 Tokyo, Japan IIJ | --- |
 Mumbai, India Google India | --- |
 Seoul, Korea KT | --- |
 Dubai, UAE Etisalat | --- |
 Sydney, Australia Telstra | --- |
 Auckland, NZ Cloudflare | --- |
 São Paulo, Brazil NIC.br | --- |
 Buenos Aires, AR Telecom Arg | --- |
 Johannesburg, ZA ISPA | --- |
 Cairo, Egypt Telecom Egypt | --- |
DNS Map
About SOA records
Every DNS zone has exactly one SOA (Start of Authority) record at its root. It names the primary nameserver and the administrator's email, then lists five timers: serial, refresh, retry, expire, and minimum. The serial number is a version tag that increases each time the zone changes. For the full breakdown, read what is an SOA record.
Each row shows one of the 21 global servers and the SOA values it returned. The most useful field is the serial. After you edit a zone, secondary servers should pick up the new serial. When every server here reports the same serial, the zone is in sync worldwide. A server showing an older serial has not refreshed yet.
The minimum field sets how long negative answers (name does not exist) are cached. A high value means a missing record stays missing in caches for a while even after you add it. If a newly added name is not resolving, a long negative cache from the SOA minimum can be the reason, so check the SOA when troubleshooting missing records.