DNS Records

Resolve the six core record types for a domain — A, AAAA, MX, NS, TXT and SOA — in one pass. Bulk mode handles up to 100 domains at once and the full record set lands in a single comparison table.

Free to use, no signup. On the next page you confirm before we run the check.

What this check returns

Domain: The domain name that was queried.
A: IPv4 address(es) the domain resolves to (A records).
AAAA: IPv6 address(es) the domain resolves to (AAAA records).
MX: Mail servers that accept email for the domain, with priority.
NS: Nameservers listed in DNS for the domain.
TXT: TXT records — often SPF, verification tokens and policies.
SOA: Start of Authority record — primary nameserver and zone serial.

Complete DNS records lookup

Resolve six record types for a domain in one request — A, AAAA, MX, NS, TXT and SOA — and run it across up to 100 domains at once. Whether you're troubleshooting email delivery, verifying a migration, or auditing your zone, the full record set lands in a single comparison table without copy-pasting between dig invocations.

What is a DNS record?

DNS (Domain Name System) records are entries stored on authoritative name servers that tell the rest of the internet how to reach the services behind a domain — which IP address to connect to, which mail server to talk to, which TLS keys to trust, and dozens of policy hints in between. Most outages and email-delivery problems are, in the end, a DNS problem.

What this tool returns

Per submitted domain we resolve six record types and render them as columns in the result table — one row per domain in bulk mode, a detailed card for a single lookup. Multi-value records appear inside the same cell (A and NS are comma-separated; MX and TXT use one record per line).

Domain: The hostname you submitted, after trimming whitespace and surrounding dots.
A: IPv4 address(es) the hostname resolves to. Multiple A records mean DNS round-robin or a pool behind a load balancer.
AAAA: IPv6 address(es). An empty cell means the domain is IPv4-only.
MX: Mail exchangers as priority host pairs, lower priority wins. Bad MX is the most common cause of inbound delivery failure.
NS: Authoritative name servers as listed in DNS — useful for spotting half-finished registrar transfers when they disagree with the registrar-side NS.
TXT: Every TXT record on the domain, one per line. This is where SPF, DKIM (under a selector), DMARC and various ownership-verification tokens (Google, Microsoft, Atlassian, etc.) live — read the raw strings here.
SOA: Primary name server for the zone plus the zone serial number, formatted as mname / serial N. Useful when diffing two views of a zone after a change.

What this tool doesn't show: TTL values, CNAME, SRV, CAA, PTR (reverse DNS), DNSKEY/DS/RRSIG, and the DNSSEC-validated status of any answer. If you need one extra record type per row stitched together with GeoIP and ASN data, use the domain & IP bulk lookup and pick a type (MX / NS / TXT / A / AAAA / CNAME) from the Additional DNS lookup dropdown.

Other DNS record types you should know about

Even though this tool focuses on the six above, here's how the rest of the common record types fit in:

CNAME — alias from one hostname to another. Cannot coexist with other records at the same name; never set on a zone apex.
SRV — locator (host + port) for services like SIP, XMPP, Minecraft and Microsoft 365.
CAA — which certificate authorities may issue TLS certificates for the domain. A no-brainer hardening step.
PTR — reverse DNS, lives on the IP side (in-addr.arpa / ip6.arpa). Mail servers check it before accepting a sender.
DNSSEC (DS / DNSKEY / RRSIG) — cryptographic signatures that prove a record really came from the authoritative server.

Why look DNS up?

Email problems

When mail bounces or goes to spam, work top-down: MX (does mail even arrive?), TXT for SPF/DKIM/DMARC (is the sender authenticated?), then check the receiving side via the email deliverability check.

Website outages

A / AAAA pointing at the right host is step one. If A resolves but the site doesn't load, the DNS is fine and the issue is upstream (firewall, web server, certificate).

Migration verification

Before and after switching DNS provider or hosting, run the full record set as a snapshot — easy to diff later.

Security & hygiene

Audit SPF/DKIM/DMARC in TXT records, check for orphaned entries, and confirm authoritative NS hasn't drifted from what's at the registrar.

Bulk mode

Drop up to 100 domains in the textarea, one per line. We run the same six lookups for each one and render the result as a wide comparison table you can scroll horizontally and export. Supported export formats: CSV, JSON, YAML, XML. Great for portfolio audits, post-migration verification, or building an inventory before you touch anything.

What you can verify here

The result table is a fixed snapshot — record values only, no TTL, no propagation status. With that in mind, this tool is well suited to:

Confirming a domain has both A and AAAA.
Reading MX priorities and targets to debug inbound mail.
Pulling out the SPF, DKIM (when you submit the selector subdomain — e.g. selector._domainkey.example.com) and DMARC strings from TXT.
Checking that the authoritative NS set matches what the registrar published.
Diffing the SOA serial before and after a zone change.

And what it isn't: this tool doesn't show TTLs, so it won't help you tune cache lifetimes. It doesn't return CAA, so it can't confirm which CA may issue your TLS cert. It doesn't return PTR, so reverse-DNS for mail senders has to be checked elsewhere.

Troubleshooting cheatsheet

Site won't load: Check A / AAAA. If they're right and the site still fails, you've ruled DNS out — investigate the host or CDN next.
Mail bouncing: Confirm the MX target hostnames resolve in their own A/AAAA columns when you submit them. Then verify SPF and DMARC in the TXT cell of the sending domain.
DKIM selector missing: DKIM keys live under {selector}._domainkey.{domain}. Submit that fully-qualified hostname to pull the public key out of TXT.
Zone change not visible: Compare the SOA serial before and after. If it hasn't bumped, your provider hasn't published the change to the authoritative servers yet.
Registrar / DNS provider drift: Compare the NS column here with the NS shown by the WHOIS tool. If they disagree, a registrar transfer or NS change is half-done.

Limitations

Lookups happen from our resolver, not from your network — local NXDOMAINs and split-horizon DNS aren't visible here.
Only the six record types listed above are returned. No CNAME, SRV, CAA, PTR or any DNSSEC record.
No TTL is shown — the result table is record content only.
SOA is collapsed to mname / serial N — refresh / retry / expire / minimum are not displayed.
We don't validate DNSSEC chains; the data is what the resolver gave us.
Heavily rate-limited authoritative servers occasionally return a partial set; retrying usually fixes it.

How our service works

Validation. Each line is checked as a hostname (letters, digits, dots, hyphens, max 253 characters).
Native resolver. We call PHP's dns_get_record() for each record type — A, AAAA, MX, NS, TXT, SOA — talking to the system resolver.
Bulk fan-out. Up to 100 hosts per submission, each with its own row in the result table.
Export. CSV / JSON / YAML / XML download direct from the result page; no signup required.

Related tools

Pair this with WHOIS & RDAP lookup for registration and registrar data, domain & IP lookup for GeoIP / ISP / ASN behind each address, the email deliverability check for end-to-end SPF / DKIM / DMARC verification, and blacklist check to see whether the resulting IPs sit on any RBL.

Get started

Paste one or more domains in the form above and click Lookup. Single-domain submissions get a detailed record card; bulk submissions render as a side-by-side comparison table you can scroll horizontally and export to CSV, JSON, YAML or XML.