Per-Type Record Tables
Every record type in its own labeled table, with MX sorted by priority and TXT chunks reassembled into full strings.
DNS Records Lookup for A, MX, TXT, SPF and DMARC
DR: DNS Records Lookup checks resolve a, aaaa, cname, mx, ns, txt, soa, and caa records, then grade spf and dmarc email-auth health. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Resolve every common record type and grade email-auth posture in one pass.
Atualizado
Loading tool interface...
A, AAAA, CNAME, MX, NS, TXT, SOA, CAA resolution SPF parsing with all-qualifier detection DMARC policy and percentage grading Priority-ordered MX records Graceful NXDOMAIN and timeout handling
What does DNS Records Lookup do?
DNS Records Lookup queries the authoritative DNS for a domain and returns a clean, per-type breakdown of its A, AAAA, CNAME, MX, NS, TXT, SOA, and CAA records. It then parses the TXT records to surface the SPF policy and resolves the _dmarc record to grade its reporting policy, so you can see your infrastructure and email-auth posture in a single report.
Why it matters: DNS is the foundation of everything a crawler, browser, or mail server does with your domain. A missing A record makes a page unreachable, a misconfigured MX silently drops mail, and a permissive or absent SPF/DMARC setup lets attackers spoof your brand in inboxes, which erodes the trust signals search and email providers care about.
Full record coverage: See IPv4 and IPv6 endpoints, mail exchangers ordered by priority, authoritative name servers, and the SOA serial in one place instead of running eight separate `dig` commands.
Email-auth health: Read your SPF mechanisms and all-qualifier, plus the DMARC policy (p=none, quarantine, or reject), percentage, and reporting address, with plain-language guidance on what to fix.
Migration and launch checks: Confirm a domain is delegated, resolving, and serving the records you expect before you point traffic at it or flip a DNS cutover.
When should you use DNS Records Lookup?
DNS Records Lookup is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
Como usar esta ferramenta
- 1 Enter a domain (a full URL works too; the path is ignored).
- 2 Run the DNS records lookup.
- 3 Review the per-type tables plus the SPF and DMARC health cards.
- 4 Fix any missing records or weak email-auth policies, then rerun to confirm.
What should you do next?
After resolving DNS, audit full domain trust signals and SSL with the Domain Health checker, then grade response headers and HTTPS posture. Then move to the related checks below to confirm the fix on the live canonical page.
O que você ganha
SPF + DMARC Grading
Detects the SPF all mechanism and the DMARC enforcement policy, flagging monitoring-only and permissive setups as warnings.
Resilient Resolution
NXDOMAIN, ENODATA, SERVFAIL, and timeouts are reported clearly per record type instead of failing the whole lookup.
Frequently Asked Questions
Respostas sobre DNS Records Lookup
This tool resolves A, AAAA, CNAME, MX, NS, TXT, SOA, and CAA records in a single query. A and AAAA give the IPv4 and IPv6 endpoints, MX lists mail exchangers by priority, NS shows authoritative name servers, TXT carries SPF and verification tokens, SOA reports the zone serial, and CAA controls which certificate authorities may issue certs for the domain.
It parses your TXT records for the v=spf1 string and resolves the _dmarc subdomain for the DMARC record. SPF is graded on its all mechanism (-all hard fail is best, ?all and +all are flagged as weak), and DMARC is graded on its policy: p=reject and p=quarantine pass, while p=none is treated as monitoring-only and earns a warning.
An empty result usually means the domain simply does not publish that record type, which is often normal. A site with no email, for example, may have no MX, SPF, or DMARC records. The tool distinguishes a genuinely empty record set from a non-existent domain (NXDOMAIN) and from a lookup that timed out, so you can tell the difference at a glance.
DNS responses are cached at multiple layers, so recent zone edits can take time to appear everywhere as TTLs expire. This tool queries authoritative DNS to minimize stale answers, but if you just changed a record, allow time for propagation. Geographically split (GeoDNS) and load-balanced setups can also return different addresses to different resolvers.