HomeFree ToolsDNS Record Lookup
Domain Infrastructure • Live DNS-over-HTTPS
DNS Record Lookup Tool
Resolve A, AAAA, MX, TXT, CNAME, NS, SOA, CAA and PTR records for any domain — live, with TTLs, in a single pass.
Verify mail routing, nameserver delegation, SPF/DKIM/DMARC strings, subdomain wiring and certificate authority policy without installing dig or shelling into a terminal.
9 Record Types
A to PTR in one pass.
Live Queries
Google DNS-over-HTTPS.
TTLs Shown
Propagation at a glance.
No Sign-Up
Nothing to install.
DNS Record Lookup
Nine record types — A, AAAA, MX, TXT, CNAME, NS, SOA, CAA and PTR — resolved live with TTLs, no sign-up.
Querying authoritative resolvers…
Worked example — example.com
Captured 22 October 2026 via Google DNS-over-HTTPSThis is the shape of a real result, for the IANA-reserved example.com, so you can see what each record type means before you run your own lookup. Records change — run a live lookup for the current answer.
| Record | Answer | TTL | What it tells you |
|---|---|---|---|
| A | 104.20.23.154, 172.66.147.243 | 300 | The IPv4 addresses the hostname resolves to — the addresses a browser would connect to. |
| AAAA | 2606:4700:10::ac42:93f3, 2606:4700:10::6814:179a | 300 | The IPv6 addresses. Published in parallel with the A records, so dual-stack clients are not forced onto IPv4. |
| CNAME | No record published | — | The apex is served directly rather than aliased to another name — a CNAME would shadow every other type at the same label. |
| MX | 0 . | 125 | A null MX (RFC 7505): the domain explicitly declines all mail instead of silently falling back to an A record. |
| TXT | v=spf1 -all (plus one domain-verification string) | 300 | The SPF policy — only this host may send mail, every other sender is rejected — alongside a domain-ownership token. |
| NS | hera.ns.cloudflare.com., elliott.ns.cloudflare.com. | 21600 | The authoritative name servers for the zone. A registrar change is only live once these change too. |
| SOA | elliott.ns.cloudflare.com. dns.cloudflare.com. 2418004112 10000 2400 604800 1800 | 1800 | Zone serial, refresh, retry, expiry and minimum TTL — the values every second-level name server copies from. |
| CAA | No record published | — | No certificate-authority restriction, so any public CA may issue a certificate for this name. |
| PTR | No record published | — | Reverse DNS for 104.20.23.154 returned nothing — mail servers that require a matching PTR will reject it. |
What is a DNS record lookup used for?
A DNS record lookup translates a human-readable name into the machine-readable answers that run the internet: which IP a domain points to (A/AAAA), where mail is delivered (MX), what verification and policy strings are published (TXT), which name servers are authoritative (NS), plus the zone's SOA serial, CAA certificate authority policy and reverse DNS (PTR). A 2024 Cisco study put the global average DNS lookup at roughly 16 ms — cheap enough that a wrong record is almost always a configuration mistake, not a network one. This tool runs all nine query types against Google's DNS-over-HTTPS resolver and shows every answer with its TTL.
1. The Nine Record Types, and What Each One Tells You
Most production incidents trace back to one of these records being missing, stale or pointing at the wrong host:
| Record | Answers | Common Debugging Task |
|---|---|---|
| A / AAAA | IPv4 / IPv6 address of the host. | Confirm a domain points at the right server or CDN edge after a migration. |
| MX | Mail exchangers with priority values. | Verify Google Workspace / Zoho records and catch-all priority order. |
| TXT | SPF, DKIM, DMARC and site verification strings. | Debug bounced mail, missed verification, or a missing _dmarc policy. |
| CNAME | Alias to another name. | Check www and CDN aliases resolve, and that nothing shadows other types. |
| NS / SOA | Authoritative name servers and zone serial. | Confirm a registrar change actually propagated and the zone is serial-synced. |
| CAA / PTR | Allowed certificate issuers; reverse DNS. | Explain Let's Encrypt validation failures and mail server reverse-PTR checks. |
2. Reading the Output: TTL, Priority and Shadowing
Three details in the result table decide how quickly your change takes effect and whether it is visible at all:
How long resolvers may cache the answer. A 300s TTL means changes surface in about five minutes; a 86400s TTL can hold an old answer for a day. Lower TTLs before a planned migration, raise them back afterwards.
Lower number wins. A typo turning 1 into 10 silently re-routes mail to a backup server — or off the domain entirely.
A CNAME at a name makes other record types at that same name invisible (except at the zone apex, where CNAMEs are invalid). If MX or TXT "disappears", look for a stray CNAME first.
"No record published" is an answer, not an error — it usually means the record was never created on the exact host (_dmarc, mail, a selector) you intended.
3. Why DNS-over-HTTPS Instead of Legacy dig Over UDP/53
Plain DNS queries travel unencrypted and are trivially intercepted on hostile or captive networks. This tool uses DNS-over-HTTPS (RFC 8484) against Google's public resolver, giving three practical advantages:
- Bypasses local tampering: ISP hijacking, search-assistant DNS rewriting and captive-portal interception cannot distort the answers.
- No tooling to install: the same nine queries you would otherwise assemble by hand in a terminal, run from any browser — including a phone during an incident bridge.
- Consistent global view: you see one resolver's authoritative-ish answer rather than whatever your laptop's current network hands you, which makes two people comparing results agree.
DNS That Keeps Breaking?
We audit the zone, flatten bloated SPF records inside the 10-lookup limit, stage DMARC to p=reject and clean up subdomain and redirect wiring — as a fixed-scope task.
SPF, DKIM & DMARC Checker
Grade email authentication for the same domain — SPF lookup limits, DKIM selectors and DMARC policy enforcement.
Check email authWHOIS & Registration History
Registrar, creation and expiry dates for the same name via ICANN RDAP.
Inspect registrationDNS Lookup FAQs
Record types, TTL behaviour, empty answers and how DNS-over-HTTPS differs from plain dig.
What is a DNS record lookup?
A DNS record lookup asks a name server how a domain resolves — which IP address it points to (A/AAAA), where mail should be delivered (MX), what verification and policy strings are published (TXT), which name servers are authoritative (NS), and the zone's SOA and CAA settings. This tool performs those queries live through Google's DNS-over-HTTPS resolver and shows every answer with its TTL.
Which record types does this tool check?
Nine: A, AAAA, MX, TXT, CNAME, NS, SOA, CAA and PTR. Between them they cover the checks people actually run — site IP verification, mail routing, SPF/DKIM/DMARC strings, subdomain wiring, name server delegation, zone serials, certificate authority policy and reverse DNS for sending IPs.
How current are the results?
Each query goes to dns.google (8.8.8.8's DNS-over-HTTPS endpoint) at the moment you press lookup, so you see the resolver's current view. The TTL shown with each record is how long other resolvers may cache it — after you change a record, propagation timing is governed by that TTL, not by this tool.
Why do I see fewer answers than expected for a record?
DNS returns only what exists for the exact name queried. A missing record type means it is not published (for example no DMARC record at _dmarc.yourdomain.com), while a CNAME at the same name shadows other types at that label. Query the exact host the record should live on — www, mail, _dmarc, or a selector — rather than the apex alone.
Is this tool free and does it store my queries?
Free, with no sign-up, no email gate and no rate limits on our side. The query leaves your browser and goes straight to Google's public DNS-over-HTTPS resolver — it never touches our servers, and we do not receive or store the domains you look up.
Can AnyPlace fix DNS problems this tool flags?
Yes. We audit zone files, flatten bloated SPF records within the 10-lookup limit, stage DMARC enforcement, correct nameserver delegation and clean up subdomain and redirect wiring — as a fixed-scope infrastructure task. Send the domain through the contact form and we will return a scoped plan.
Content last reviewed October 2026.
When the lookup is not enough
Infrastructure Work Behind The Record
These service pages describe the work that acts on the zone, mail and edge configuration the tool just surfaced.
- Cloud Setup & DevOpsInfra as code + runbookSetup typically 1–2 weeks per environment, then handover walkthrough
- Security Reviews & HardeningReview report + fixesReview typically 1–2 weeks, fixes scheduled by priority after that
- Business Website DevelopmentLive site + editing guideBrochure-to-lead-gen site typically 2–5 weeks after content is ready
Pairs with
The other tools that answer the same question
These run in your browser, need no signup, and send nothing to us.
WHOIS & DNS Record Inspector
Inspect authoritative ICANN registrar records, test DNS propagation, and verify email security strings (SPF, DKIM, DMARC) in real time.
Open the toolDomain Age & Registration History Checker
Calculate exact registration age, track renewal deadlines, and evaluate Google Sandbox trust maturity via real-time ICANN RDAP.
Open the toolEmail Authentication (SPF, DKIM & DMARC) Checker
Audit SPF, DKIM and DMARC records in one pass and get a spoofing-protection grade for your sending domain.
Open the toolTELL US ABOUT YOUR PROJECT
Tell Us What to Build, Fix or Modernize
Send a short brief. We reply within 12 hours with clarifying questions and a discovery quote — no retainers, no spam.
What Happens Next
Request a Discovery Quote
Share your goals and timeline. NDA signed first if needed.
12-hour response