SOA Record Propagation CheckerVerify the Start of Authority serial number is consistent across global DNS networks
- 7 independent networks
- Records + DNS flags
- No ads, no sign-up
Independent networks
7 public DNS networks, queried in parallel
Every test query is answered by these unaffiliated resolvers on separate networks and infrastructure. When they agree, you can trust the result.
- 8.8.8.8
Google Public DNS
Google LLC · North America
- 1.1.1.1
Cloudflare
Cloudflare, Inc. · Global Anycast
- 94.140.14.14
AdGuard DNS
AdGuard Software Ltd. · Europe
- 45.90.28.0
NextDNS
NextDNS, Inc. · Global Anycast
- 185.222.222.222
DNS.SB
xTom / Layer0 · Europe
- 223.5.5.5
Alibaba DNS
Alibaba Cloud · Asia
- 119.29.29.29
DNSPod
Tencent Cloud · Asia
How it works
A test query for flag propagation check, done right
Most checkers query a single resolver or a set of geographically labelled servers behind the same anycast network. isPropagated queries genuinely independent DNS operators and compares both their records and their response flags.
Enter a domain and run the test query
Type any domain, pick a record type (A, AAAA, CNAME, MX, TXT, NS and more), then run a single test query that fans out to every network at once.
We query independent global networks
Instead of asking one resolver, we ask several unaffiliated public DNS networks in parallel — across North America, Europe and Asia — so no single cache can mislead you.
Compare records and DNS flags
Each network returns its answer plus the DNS response flags (AD, CD, RA, RD, TC). We check that both the records and the flags agree before calling a domain propagated.
Read the propagation verdict
A clear consensus score shows how many networks resolved the record and whether their answers match — so you know the moment a change is live everywhere.
What is an SOA record and what does it tell you about propagation?
The SOA (Start of Authority) record is the first record in every DNS zone. It contains the primary nameserver, the zone administrator's email address, and a serial number that increments every time the zone is modified. Secondary nameservers use the serial number to decide whether to pull a fresh zone copy from the primary — a higher serial triggers a zone transfer.
Checking SOA records across independent resolvers is a reliable way to confirm that a zone update has reached all nameservers. If all resolvers return the same serial number, they have all refreshed their copy of the zone and subsequent changes should resolve consistently. Mismatched serial numbers indicate that secondary nameservers are still serving a previous version of the zone.
SOA records also contain the zone's negative-cache TTL — the MINIMUM field — which controls how long NXDOMAIN responses are cached. A high MINIMUM value (e.g., 3600) means resolvers cache "this name does not exist" for up to an hour, which matters when you add a new record to a zone.
SOA serial numbers and zone consistency
Enter your domain name (e.g., example.com), select SOA from the type dropdown, and run the test. Each resolver card shows the full SOA record including the serial number. Consistent serial numbers across all 7 resolvers means the zone is in sync everywhere.
A common convention is to use a date-based serial like YYYYMMDDNN (e.g., 2024121001). Many DNS providers increment serials automatically. If you manage your own nameservers and the serial is not incrementing, secondary nameservers will not pull zone updates.
FAQ
Common questions about soa record propagation checker
How do I read a SOA record result?
The data field shows: primary nameserver, admin email (dots replace @ in DNS format), serial number, refresh interval, retry interval, expire time, and negative-cache TTL. The serial number is the most useful field for checking propagation — all nameservers should agree on it.
Why do my SOA serial numbers differ across resolvers?
If your SOA serial numbers differ between resolvers, one or more secondary nameservers have not yet performed a zone transfer to pick up the latest changes. Check that your nameserver software is configured to allow zone transfers and that the REFRESH interval in the SOA has not expired without a successful transfer.
How often do secondary nameservers check for zone updates?
Secondary nameservers check the primary's SOA serial at the REFRESH interval specified in the SOA record (commonly 3600–86400 seconds). They also re-check after the RETRY interval on a failed refresh. Modern DNS providers use NOTIFY messages to push zone change notifications instantly, bypassing the REFRESH delay.
What is the SOA MINIMUM field used for?
The MINIMUM field (last value in the SOA record) sets the negative-cache TTL — how long resolvers cache "this name does not exist" responses. A MINIMUM of 3600 means NXDOMAIN responses are cached for an hour. To speed up propagation of newly added records, temporarily lower the MINIMUM before adding them.