Resolve any DNS record
A, AAAA, MX, TXT, CNAME, NS, SOA, CAA, SRV, PTR via Cloudflare DNS-over-HTTPS. Runs entirely in your browser.
How to resolve DNS records
Pick a record type, enter a domain, hit Lookup.
- 01
Enter a domain
Apex (
example.com) or any subdomain.Lookups reference the IANA registries (MIME, HTTP status, TLDs) bundled at build time — no live network calls, no rate limits, no leaked queries.
inputIANAregistryofflineliveinput · querydomain · IANAexample.com
loaded · IANA bundlespec · ready - 02
Pick a record type
A and AAAA for addresses, MX for mail, TXT for verification, CAA for cert authorities.
Builders emit canonical syntax per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs) so the output passes spec-compliant parsers.
typeRFC 9110canonicalspec-compliantlivetype · optionsMX · liveMX 10 mail.example.com
options applied · livecanonical - 03
Read the answers
Each row shows type, name, TTL, and data.
Validation flags common pitfalls — uppercase header names, smart quotes inside
Content-Type, missing;charset=utf-8— before they bite production.answervalidationlintpitfallslivettl · looked up300 · readyA example.com TTL 300 93.184.216.34
result · livevalidated - 04
Copy or download
Grab a tabular dump of the response.
Copy writes the snippet directly into your clipboard; downloads emit the right extension and MIME so curl/httpie pick them up correctly.
exportclipboardMIME-correctblobcurl-readyok · copiedready · doneCopied
shipped · ready to shipsuccess
Web-spec details that bite later
Idempotency saves retries
POST/PUT/DELETE should be safely retried. Use idempotency keys and return the same response on duplicate requests.
Match RFC 9110 status codes
Don’t invent codes. 422 for validation errors, 409 for conflicts, 429 for rate limits. Standard codes work with off-the-shelf clients.
Set <code>Cache-Control</code> deliberately
Default browser caching is conservative. Use max-age + stale-while-revalidate for hot endpoints.
Validate Open Graph in dev
OG tags break silently. Use a previewer like OG Generator + Facebook’s debugger before launch.
CORS is a server concern
The browser sends the preflight; the server decides. Wildcard origins disable credentials — be explicit.
MIME drives behaviour
Servers must send the right Content-Type. Browsers sniff but the spec says they shouldn’t — be explicit to avoid surprises.
When to query DNS
Debugging email, validating zones, migration.
Email setup
Verify MX, SPF, DKIM, DMARC after a config change. Bundled from IANA registries at build time — no live network call, no rate limit, no leaked queries. The MIME, TLD, and status-code tables are baked in so the tool works offline once loaded.
spec-compliantDomain migration
Watch TTLs and propagation in real time. Output is canonical per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs), so spec-compliant parsers accept it as-is. Cross-browser and cross-library behaviour stays consistent.
offlineCert issuance
Confirm CAA records authorise your issuer. Pairs with the curl-to-fetch converter for end-to-end test stubs — copy the curl from DevTools, paste, get an idiomatic fetch() body. Drop into Playwright/Vitest fixtures without manual translation.
IANA-backedCDN cutover
Verify A / AAAA point to the right edge. Catches common pitfalls (uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8) before they bite production. Validation flags rather than auto-corrects so you stay in control.
RFC-alignedOutage triage
Rule DNS in or out of an incident quickly. Validation runs as you type — copy only when the output is shaped correctly. The output drops directly into nginx, Apache, or CDN configs without re-formatting or re-quoting.
production-gradeThreat hunting
Inspect TXT or NS for unexpected entries. Same input plus same options always produces identical canonical output, so the tool is safe to embed in CI scripts that diff against expected configs.
curl-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.