Skip to content

Free DNS Record Lookup + SPF, DMARC & DKIM Email Auth Checker

See every record for a domain, and check SPF, DMARC and DKIM before your mail lands in spam.

Free · No signupQueried from your browser

DNS record lookup

Try

Records

A, AAAA, CNAME, MX, NS, TXT, CAA, SOA and HTTPS, with TTLs and where mail is hosted.

Email security

SPF with every include counted against the 10-lookup limit, DMARC policy and DKIM keys.

Compare resolvers

Cloudflare and Google side by side, to see whether a change has spread.

Only the names you look up go to Cloudflare’s public resolver, or Google’s as a fallback. Nothing reaches CtrlOps.

From the records to the server

Run the servers these records point to.

Connect over SSH, watch health and deploy apps on every server, all from one desktop workspace.

Explore deploymentsDownload for MacDownload for Windows

Keep it handy

Record types,
at a glance.

The records a lookup returns, what each one holds, and what a typical value looks like.

DNS record types, what they hold and an example value
TypeHoldsExample
AIPv4 addresses for the name93.184.215.14
AAAAIPv6 addresses for the name2606:2800:21f:cb07::1
CNAMEAn alias to another name, which answers insteadwww → example.netlify.app
MXThe servers that receive mail, lowest number first10 mx1.example.com
NSThe name servers that hold the zonens1.cloudflare.com
TXTFree text: SPF, DMARC, DKIM keys and site verificationv=spf1 include:_spf.google.com -all
CAAThe certificate authorities allowed to issue for the name0 issue "letsencrypt.org"
SOAThe zone’s primary server, admin contact and serialns1.example.com 2026102101
PTRThe name for an IP address (reverse DNS)1.1.1.1 → one.one.one.one

How the checks work

Records first.
Then the mail.

Real answers, straight from public DNS

Your browser asks Cloudflare’s DNS-over-HTTPS resolver directly, and Google’s if Cloudflare cannot be reached. A, AAAA, CNAME, MX, NS, TXT, CAA, SOA and HTTPS are fetched together, with each record’s TTL, and every mail server is resolved to check it has an address. A subdomain is looked up as written, and a CNAME is followed to the name that actually answers.

SPF counted the way receivers count it

SPF allows 10 DNS lookups. Every include, a, mx, ptr and exists term costs one, and includes nest, so the checker walks the whole tree and counts the worst case, as RFC 7208 tells receivers to. It also counts lookups that return nothing, which RFC 7208 limits to two, and flags +all, a missing all and the deprecated ptr.

DMARC and DKIM, with what to change

DMARC is read from _dmarc, falling back to the parent domain’s sp= policy for a subdomain, then checked for a real policy and a report address. DKIM keys are looked for under about 20 selectors that common providers use, plus yours, and each key’s size is estimated so weak 1024-bit keys stand out. Every problem says what to publish instead.

Compare resolvers after a change

After you edit a record, resolvers keep the old answer until its TTL runs out. Compare resolvers asks Cloudflare and Google the same questions and marks every answer that differs, so you can see whether the change has spread or is still cached.

Read RFC 7208, the SPF specification

Common questions

DNS and email,
explained.

Keep exploring

Related tools for your next task.

Your privacy preferences. We use product analytics to improve CtrlOps. Google Analytics cookies and live chat stay off until you allow them. Cookie policy