How DNS Resolution & TTL Caching Work
When a user visits your website or connects to your services, their browser does not query your authoritative nameservers on every request. Instead, queries flow through local recursive resolvers provided by ISPs or public Anycast providers (such as Cloudflare 1.1.1.1 and Google 8.8.8.8). These resolvers store the answer in cache for the duration of the record's Time-to-Live (TTL).
When you update a DNS record, resolvers worldwide will not reflect the new IP address until their existing cached TTL reaches zero. For this reason, differences in responses between resolvers are common during migrations and do not signify an outage.
Email Authentication: SPF, DKIM & DMARC
Modern email providers (including Google Workspace, Microsoft 365, and Yahoo) require strict sender authentication to protect users against phishing and domain spoofing:
- SPF (RFC 7208): Designates authorized sending IP addresses and services. Limited to a strict budget of 10 DNS lookups.
- DKIM (RFC 6376): Digitally signs message bodies and headers with cryptographic public keys published at specific DNS selectors.
- DMARC (RFC 7489): Enforces alignment between the visible From address and SPF/DKIM, instructing receivers to quarantine or reject unauthenticated mail.
Frequently Asked Questions (FAQ)
What is the difference between recursive DoH and authoritative nameserver testing? ▼
Recursive DoH queries public resolvers (1.1.1.1 and 8.8.8.8) to see what end users see across the global internet. Authoritative testing queries the specific nameservers configured at your registrar directly. While recursive lookups establish real-world client behavior, they do not prove that individual authoritative server sockets are reachable or that regional ISP caches have expired.
Why can DNS work in one location or resolver but fail in another? ▼
DNS propagation is not an instantaneous push event; it is a pull event driven by expiration of TTL timers. Different recursive resolvers query your authoritative servers at different times and maintain independent cache counters. Furthermore, Anycast CDN networks (Cloudflare, AWS, Fastly) dynamically route requests to different edge IP addresses depending on geography.
What is an RFC 7505 Null MX record? ▼
RFC 7505 specifies that a single MX record with priority 0 and target \".\" (dot) explicitly declares that the domain refuses all incoming email. When sending mail servers encounter a Null MX, they will immediately generate a bounce message without attempting delivery.
Are entered domains or pasted email headers stored or transmitted? ▼
No. All diagnostics run 100% client-side in your web browser. When you enter an email address, the local username is discarded immediately in browser memory. Message headers and delivery bounce text are parsed locally and never transmitted across the network or logged.