NS Lookup
Name servers from the NS records, with TTL.
An SOA record lookup explains the zone serial, the primary server, the responsible mailbox, and the refresh, retry, expire, and minimum timers.
This check runs on our server. The address you enter is used only for this check and is not stored.
This check runs on our server. The name is not stored.
Every zone has one SOA. The serial is a counter that secondary servers compare. When the serial matches YYYYMMDDnn, the tool also prints it as a date and a sequence, for example 2024010101 as 2024-01-01, sequence 1. A serial that is just a number stays a number. The mailbox is shown with @. In a zone file the same address is written with a dot in place of @, so hostmaster.example.com is [email protected].
Refresh, retry, and expire are seconds. They tell a secondary server how to keep its copy. The minimum field is the time resolvers may cache a "name not found" answer.
Secondaries store the last serial they copied. When the primary's serial is higher, they transfer the zone again.
The tool shows the mailbox with @. In a zone file, the first dot stands for @, so admin.example.com is [email protected].
A secondary that has not been able to refresh stops serving the zone, so it does not keep handing out a copy that may be abandoned.
Often used together with the SOA Record Lookup.
Name servers from the NS records, with TTL.
One table of A, AAAA, MX, NS, TXT, SOA, and CAA records for a domain.
One DNS question sent to about 20 public resolvers, with a match against the value you expect.