SOA checker: do all your nameservers have the same zone serial?

GitHubVersion 1.1.0

Enter a domain to compare the SOA record on each of its nameservers. A matching serial number usually means every server has the same version of the zone, and a different one can point to a server that's behind.

How to read the result

The first line says whether the SOA records agree and, if not, which serial is newest. Servers that return the same values share one row. A server with a different value gets its own row.

If the Primary and Mailbox values differ too, you're usually looking at two DNS providers. Each one writes its own SOA, so their serials can't be compared.

github.com

Example

The 4 NS1 nameservers report serial 1,656,468,023, with primary dns1.p08.nsone.net. The 4 Amazon Route 53 nameservers report serial 1, with primary ns-1707.awsdns-21.co.uk.

The checker calls 1,656,468,023 newest, but neither provider is behind. They each keep their own SOA.

Checked on 9 October 2026.

What does the SOA serial number mean?

It's the zone's version number, and it goes up with each change. Many zones use the date plus a counter, such as 2026100901, as RFC 1912 suggests. Others count from 1 or use a timestamp.

Serials wrap back to zero after 4,294,967,295, so a smaller number isn't always older. The checker compares them with RFC 1982 serial arithmetic, not as plain numbers.

What do the other SOA fields mean?

FieldWhat it means
Primary, MNAMEThe zone's main nameserver, as the zone names it.
Mailbox, RNAMEThe zone contact's email, with the first dot standing for the @.
RefreshHow often a secondary server checks the primary for changes.
RetryHow long a secondary waits to try again after a failed check.
ExpireHow long a secondary keeps answering when it can't reach the primary.
MINIMUMOne of the two values that set the negative cache time.
SOA TTLHow long resolvers cache the SOA record itself.
Negative cacheHow long resolvers cache a missing name or record: the lower of the SOA TTL and MINIMUM.

All times are in seconds. Refresh, retry, and expire drive classic zone transfers. Many hosted DNS providers sync their servers another way, so these may not do anything there. The negative cache rule comes from RFC 2308.

Why do my nameservers show different serials?

  • A change is still syncing. Check again in a few minutes.
  • The domain uses two DNS providers, each with its own SOA. Compare the record you care about instead.
  • A secondary server stopped updating. It may not reach the primary, or may not be allowed to copy the zone. If its serial stays behind, fix the transfer or remove the server. The nameserver checker shows which servers are listed.

Matching serials don't prove that every record matches. To check one record across servers, use the DNS change checker.

The check asks each nameserver directly from stack127's server. IPv6 addresses are skipped when the checker has no IPv6 route. stack127 doesn't keep the names you check.