Skip to content

Free tool · Two resolvers

Look up any DNS record
in two seconds

dig, without the terminal: query any record type against Cloudflare or Google, see real TTLs, and share the result as a link.

Queries go straight from your browser to the resolver over DNS-over-HTTPS — the names you look up never touch our servers.

The records that decide whether your email lands

MX — can you receive?

Cold email exists to get replies, and replies need somewhere to land. A sending domain without MX records looks like a spam cannon to receivers.

TXT — are you authenticated?

SPF lives at the root, DKIM under selector._domainkey, DMARC under _dmarc. Three TXT lookups tell a receiver everything about whether to trust you.

A / AAAA — do you exist?

Receivers sanity-check that a sending domain has a real web presence. A domain with no A record and no website is a classic burner-domain signal.

CNAME — who's answering for you?

Tracking domains, some DKIM keys and most white-labeled services work through CNAMEs. When a vendor integration breaks, this is usually where to look.

Questions, answered honestly

How is this different from running dig in a terminal?

Functionally it's the same query — we ask Cloudflare's or Google's resolver over DNS-over-HTTPS and show you the raw answers with TTLs. The differences: no terminal needed, results are shareable as a URL, and you can flip between two resolvers in one click to compare propagation.

Why would I query two different resolvers?

Propagation. After you change a record, resolvers serve their cached copy until the TTL expires — so Cloudflare might show your new value while Google still has the old one. Comparing both tells you whether 'it's not working' means 'it's wrong' or just 'it's still propagating'.

What does the TTL column mean?

Time-to-live: how many seconds a resolver may cache this answer. A TTL of 300 means changes show up within 5 minutes; 86400 means up to a day. Pro move: lower the TTL a day before planned DNS changes, restore it after.

Which record types matter for email?

MX (where your mail arrives), TXT (where SPF, DKIM and DMARC live), A/AAAA (web presence — receivers do check that a sending domain has one), and CNAME (how tracking domains and some DKIM keys are delegated). This tool queries all of them, plus NS, SOA and CAA.

Is the lookup private?

The query goes straight from your browser to the resolver you pick, over encrypted DNS-over-HTTPS. The names you look up never touch our servers — we couldn't log them if we wanted to.

Tired of checking records by hand?

Norbelys checks the DNS that matters for email automatically — on connect and continuously after — so you only open a lookup tool when you're curious, not when you're on fire.

Start sending

From $29/mo · Cancel anytime