How to use the DNS lookup tool
Enter a domain or subdomain, such as example.com or mail.example.com, and press Lookup DNS. By default the tool fetches every supported record type in one go. To focus on one type, pick it from the row of buttons under the search box. You can paste a full URL; the tool removes the https:// prefix and any path for you.
Every lookup runs live when you submit the form. Results are not cached by this site, so you see what the public DNS returns at that moment, including the TTL each record is currently being served with.
Record types this tool checks
| Type | What it does | Example value |
|---|---|---|
| A | Points a name to an IPv4 address. | 93.184.215.14 |
| AAAA | Points a name to an IPv6 address. | 2606:2800:21f:cb07::1 |
| CNAME | Makes one name an alias of another. A name with a CNAME cannot hold other records. | shop.example.com → shops.myshopify.com |
| MX | Lists the servers that receive email for the domain, with a priority (lower is tried first). | 10 mx1.example.net |
| NS | Names the authoritative nameservers that hold the domain's DNS zone. | ns1.example-dns.com |
| TXT | Free text, used for SPF, DMARC, DKIM and ownership verification codes. | v=spf1 include:_spf.google.com -all |
| SOA | Zone administration data: primary nameserver, contact, serial number and timers. | serial 2026111101 |
| CAA | Lists the certificate authorities allowed to issue SSL/TLS certificates for the domain. | 0 issue "letsencrypt.org" |
Reading the results
TTL (time to live)
The TTL is the number of seconds a resolver may cache a record before asking again. If you change a record, visitors whose resolver cached the old value can keep seeing it until that time runs out. Lowering the TTL a day before a planned migration makes the switch-over faster.
"No records found" versus "lookup failed"
These mean different things. No records found means the DNS answered and the domain simply has no record of that type, which is normal (many domains have no AAAA or CAA records). Lookup failed means no usable answer came back at all, for example because the nameservers timed out or returned an error. A failure is worth investigating; an empty result often isn't.
Multiple A or MX records
Seeing several A records is common. Large sites spread traffic across several servers, and resolvers rotate the order. Several MX records give mail servers a fallback when the preferred server is unavailable.
Why other DNS checkers may show different answers
- Caching: each resolver keeps its own cached copy until the TTL expires, so right after a change some resolvers have the new value and some still have the old one.
- Location-based DNS: CDNs and large providers return different IP addresses depending on where the query comes from. Two correct answers can legitimately differ.
- Split or stale nameservers: if a domain's nameservers disagree with each other, results depend on which one answered. The NS Lookup tool checks every nameserver individually and compares their SOA serial numbers.
Common jobs this tool helps with
- After moving a website: confirm the A and AAAA records point at the new host before you cancel the old one.
- Setting up a service: check that a verification TXT record (Google, Microsoft 365 and others) has been published exactly as given.
- Email problems: check MX and the SPF TXT record, then run the DNS Health Checker for a full SPF and DMARC review.
- Before requesting an SSL certificate: make sure any CAA record allows your certificate authority, otherwise issuance will be refused.
Running the same lookup from the command line
On macOS or Linux, dig gives the same information:
dig example.com A +short
dig example.com MX
dig @1.1.1.1 example.com TXT # ask a specific public resolverOn Windows, use nslookup in Command Prompt or Resolve-DnsName in PowerShell:
nslookup -type=MX example.com
Resolve-DnsName example.com -Type TXTRelated tools and guides
Frequently asked questions
Is this DNS lookup tool free?
Yes. It is free to use, with no sign-up. To keep the service available for everyone, very rapid repeated lookups from one address are briefly slowed down.
Can I look up a subdomain?
Yes. Enter the full name, for example blog.example.com or _dmarc.example.com. Records are stored per name, so a subdomain can have completely different records from the main domain.
Why does my apex domain show no CNAME record?
The DNS standard does not allow a CNAME at the root of a domain (example.com) because the root must also hold SOA and NS records. Providers that offer "CNAME flattening" or "ALIAS" records resolve the target themselves and publish ordinary A/AAAA records, which is what you will see here.
How long does a DNS change take to show up?
Changes to a record are usually visible within the record's previous TTL, often minutes to a few hours. Changing a domain's nameservers at the registrar can take up to 48 hours, because the parent zone's NS records commonly have long TTLs.
Does this tool store the domains I look up?
No. The lookup runs for your request only and the domain is not saved. See the Privacy Policy for details.