DNS & WHOIS Lookup
Look up DNS records and domain registration info for any domain.
Looks up DNS records and domain registration info. Browsers cannot query DNS or WHOIS directly, so the domain you enter is sent to our server to run the lookup — see the FAQ below.
Enter a domain to look up its DNS records.
About the DNS & WHOIS Lookup
Look up a domain's DNS records — A, AAAA, MX, NS, TXT, and CNAME — alongside its registration details: registrar, registration date, expiry, and nameservers. Useful for verifying a DNS change propagated, debugging email delivery, or checking when a domain is due for renewal.
How to use it
- 1 Enter a domain name, e.g. example.com.
- 2 Click Lookup.
- 3 DNS records appear grouped by type; registration details appear below them.
- 4 A record type with no results simply means the domain has none of that kind.
What it does
- A, AAAA, MX, NS, TXT, and CNAME records via DNS-over-HTTPS
- Registrar, registration date, expiry date, and nameservers via RDAP
- Each record type fails independently — one missing record type does not block the rest
- Clear message when a TLD has no RDAP server yet, instead of a silent empty result
Frequently asked questions
Is my lookup sent anywhere?
Partly. Browsers have no API for this, so the value you enter is sent to our server, which queries Cloudflare's public DNS resolver and the domain's RDAP server on your behalf and returns the result — nothing is logged or stored beyond that single request. Avoid looking up anything you would not want to leave your browser at all.
What is RDAP, and why not WHOIS?
RDAP (Registration Data Access Protocol) is the modern, structured-JSON replacement for WHOIS, which is a decades-old plain-text protocol that every registry formats slightly differently. ICANN requires RDAP support for gTLDs (.com, .org, .dev, etc.); some ccTLDs have not adopted it yet, which surfaces here as "this TLD may not support RDAP yet" rather than a fabricated result.
Why does a record type show no results?
Not every domain has every record type — a domain with no mail server simply has no MX record, and that is correctly reported as empty rather than an error. An actual error (e.g. a resolver timeout) is shown separately from "no records exist."
How fresh are these results?
DNS records reflect what is live right now at the resolver queried — the same live lookup a mail server or browser would perform, not a cached snapshot. A record you just changed may take time to show the new value if its previous TTL has not fully expired everywhere.