DNS lookup

DNS lookup — dig in your browser

Query any record type against Cloudflare or Google over encrypted DNS-over-HTTPS — no server between you and the resolver. Paste a domain, URL or IP (IPs auto-switch to reverse lookup), compare all three resolver caches to watch a change propagate, and run a one-shot domain health audit covering nameservers, SOA, DNSSEC, CAA and wildcard catch-alls.

Where your query goes: lookups travel straight from your browser to the public resolver you pick — Cloudflare or Google — over encrypted DNS-over-HTTPS. BRev has no server in the path and never sees a lookup. The resolver you choose does see the queried name, under its own policy: Cloudflare's privacy commitment · Google Public DNS privacy.

Privacy-first public resolver. The baseline answer.

DNSSEC (DO) CD

Domain healthone-shot pure-DNS audit — NS, SOA, apex, www, CAA, DNSSEC, wildcard

Enter a domain above and run the audit — 8 queries, all from your browser. Email posture (MX, SPF, DKIM, DMARC) lives in the email DNS checker.

DNS in one minuterecords, TTLs and propagation

DNS is the internet's address book: it turns a name like example.com into the addresses and service endpoints machines actually connect to. Every record has a type (what kind of fact it states) and a TTL (how long resolvers may cache it).

Record types

Type	What it stores
A	IPv4 address
AAAA	IPv6 address
CNAME	Canonical name (alias)
MX	Mail exchanger (priority target)
TXT	Text — SPF, verifications, DKIM, arbitrary data
NS	Authoritative nameservers
SOA	Start of authority (serial, refresh, retry, expire, minimum)
SRV	Service locator (priority weight port target)
CAA	Which CAs may issue certificates
PTR	Reverse DNS (IP → name)
DNSKEY	DNSSEC public key
DS	Delegation signer (DNSSEC chain of trust)
HTTPS	HTTPS service binding (ALPN, ECH, hints)
SVCB	General service binding
TLSA	DANE — pin certificates in DNS
NAPTR	Name authority pointer (SIP/ENUM)

TTL & “propagation”

DNS changes don't “push” anywhere — resolvers simply keep the old answer until its TTL runs out, then fetch the new one. So a change “propagates” in at most the old record's TTL. Planning a change? Lower the TTL (e.g. to 300s) a day in advance, make the change, then raise it back. The compare card above shows whether major public caches have picked your change up yet.