DNS Lookup
Every record for a domain, where it comes from and whether it’s healthy.
Asked from our server in Newark, US · our resolver and the domain’s own name servers
Press Look up to map mongodb.com
- The domain
- Record type
- Answer
- Unverified
- Network · ≈ place
The lookup’s journey New
Findings New
Counted, never scoredThe constellation, as a list
Every star above is a row here, and every row is a star. Hover one to light the other.
Findings New
What stands out, counted by state. Never a score.
Every record
TTL is how long a copy may be kept; “cached” is what our resolver’s copy has left.
Name-server health New
Each of the domain’s name servers, asked from our server in Newark, US for the zone’s serial number over UDP and TCP.
Who hosts it New
The network behind each address, its reverse name and roughly where it is, with our server and the name servers on the map.
Email setup New
Who receives the domain’s mail, and the records that stop others sending as it.
How we checked
The lookup followed from the root servers down, our resolver compared with the source, and DNSSEC.
Recent lookups
Kept in this browser only.
Kept in this browser only · nothing is sentNeed many countries? DNS Propagation Checker
What the DNS lookup shows
DNS turns names like example.com into the addresses, mail servers and settings that make a domain work. This tool asks our server in Newark, US for up to 12 types of record at once, each with its value, its TTL (how long a copy may be kept) and what our resolver’s cached copy has left.
Each type is also asked straight from the domain’s own name server, so you can see whether the cached copy matches the source. It also follows the lookup down from a root server, checks DNSSEC and name-server health, and reads the email setup.
How to use it
- Type a domain name, such as example.com, or an IP address for its reverse name.
- Choose a record type, or All to see every type at once.
- Press Look up. Share link copies a link to the same lookup; the copy buttons give dig output, a zone file or JSON.
Understanding the results
A and AAAA records hold IPv4 and IPv6 addresses; we show the network behind each address and roughly where it is (approximate, IP location by DB-IP). MX records list mail servers, lowest number first. TXT records carry SPF rules and site-verification codes. NS and SOA describe who runs the zone; CAA lists the certificate authorities allowed to issue certificates. SRV tries six common service names, such as _imaps._tcp.
DNSSEC is checked in two parts: a validating resolver (Cloudflare’s 1.1.1.1) gives the verdict, and our server checks that the DS record at the parent matches one of the zone’s keys, by key tag and digest. We don’t check the signatures ourselves.
Name-server health asks each name server for the zone’s SOA over UDP and TCP, up to 2 seconds each. One that serves an older serial hasn’t picked up the latest change. SPF lookups are counted as RFC 7208 counts them, following includes five levels deep; the limit is 10.
DNS lookup questions
Why don’t I see DKIM?
DKIM keys sit under a selector name only the sender knows, so a lookup can’t list them. Check one with the SPF & DMARC checker.
Why is the answer different on my computer?
Your computer asks another resolver, which may hold an older copy until its TTL runs out. The DNS propagation checker compares many resolvers.
What does SERVFAIL mean?
Our resolver couldn’t get an answer it trusts, often because DNSSEC is broken. If the domain’s own name server still answers, we show that answer marked unverified.
Can I look up an IP address?
Yes: type the address to see its reverse name (its PTR record) and the network it belongs to.
Are lookups stored?
Each result is kept on our server for 30 days, so you can make a PDF report of it that anyone can verify on our site. Recent lookups stay in your browser.