Enter a domain and choose a record type. TTL shows how long a record may be cached, in seconds; lower MX preference numbers take precedence. Queries are sent to KivTools; this tool does not compare DNS propagation across multiple locations.
Enter a domain name and pick a record type, or leave ALL to query every type this tool supports: A, AAAA, CNAME, MX, TXT, NS, SOA and CAA. PTR takes an IPv4 or IPv6 address and returns the hostname that address points back to.
The lookup runs on the KivTools server and shows the rows the resolver returns: type, owner name, value, and the TTL in seconds that the resolver may keep caching the answer for.
A and AAAA rows carry the IPv4 or IPv6 address the resolver returned. MX rows carry the mail host and its preference number, where the lowest number is tried first. NS rows name the authoritative nameservers, and a SOA row shows the primary nameserver and the responsible mailbox separated by a middle dot. CAA shows the flags, the tag and the value a certificate authority has to match.
A TXT value is joined back into one string when the record was published in several character strings, which is how long DKIM and SPF records travel, so what is shown here is what a receiving server reassembles. The TTL is the cache time the resolver still allows, not the TTL configured in the zone: the same name queried twice in a row can come back with a much smaller number.
When a name is a CNAME, the lookup follows the chain, prints each hop, and queries the canonical name. This matters for DKIM and SPF selectors, which are usually aliases at a mail provider: the value is published on the target, not on the name you typed.
An empty list means the resolver returned no record of that type for that name, which can be a missing record, a name that does not exist, or a record that is only cached elsewhere. PTR needs an address, the other types need a name with at least two labels, and private, reserved or local addresses are refused before any query is sent.
Each lookup is one query through the resolver configured on the KivTools server, from a single location. It reports what that resolver knows at that moment; it is not a propagation map, so a change made minutes ago can still be invisible here.
The name and the record type are sent to KivTools for the query and no result is stored. The answer is not authoritative: confirm a value against the authoritative nameserver or a second resolver before you change production DNS.