DNS Lookup
Queries a public record from our server — not your files.
Query any domain for the record type you need and get the answer with its TTL, its DNSSEC status, and a note on what it means. Unlike the rest of this site, this tool cannot run in your browser — there is no DNS API in a web page — so the name you enter is sent to our server, which asks the 1.1.1.1 public resolver and sends the answer back. It queries a public record; it never touches a file on your device.
This tool is an exception on this site. Everything else here runs entirely in your browser, but a web page cannot query DNS, read a certificate or see another site’s response headers — so the name or URL you enter is sent to our server, which looks up the public record and sends the answer back. The answer is cached for up to a minute. No file of yours is read, uploaded or stored, and there is no account.
How to use DNS Lookup
- 1
Enter a domain name — example.com, or a full URL, which is trimmed for you.
- 2
Choose the record type. A and AAAA are addresses, MX is mail, TXT holds SPF and verification strings.
- 3
Read the records with their TTLs, and the notes explaining anything unusual about the answer.
Share
Embed this tool on your site
Paste this where you want the tool to appear. It runs entirely in your visitor's browser — no uploads, no account, no tracking.
Please keep the attribution line — it's what keeps these tools free.
Need a different size, a dark theme, or a different tool? Build an embed lets you preview it first.
Frequently asked questions
Does this send my data anywhere?+
It sends the domain name you type. Our server queries Cloudflare's public 1.1.1.1 resolver with it, caches the public answer for up to a minute so a repeated check is not a repeated query, and returns it. That is the whole exchange — no file, no account, nothing about you beyond the name you asked about, which is by definition public information.
I added a record and it is not showing up.+
Two delays stack up. Your provider takes a moment to publish the change to its nameservers, and every resolver that already asked is holding the previous answer until its TTL expires — including a negative answer, whose lifetime comes from the SOA record rather than the record you added. Lower the TTL before a planned change, not after.
Why does the result differ from what my computer sees?+
Because this asks a public resolver from our server, and your computer asks whatever resolver your network hands it — often your router, your ISP, or a corporate DNS server with its own internal overrides. A name that resolves differently inside an office is normally a split-horizon setup doing exactly what it was configured to do.
What is the TTL for?+
How many seconds a resolver may keep the answer before asking again. 3600 means an hour, so a change can take an hour to be seen everywhere. It is a trade: a low TTL makes changes fast and every lookup a real query, a high one is efficient and slow to correct.
What does DNSSEC "validated" mean here?+
That the resolver checked a chain of signatures back to the root and the answer had not been altered in transit. Most domains are unsigned, so "not validated" is the common case and not a fault — it simply means there was no signature to check.