Instant DNS Sandbox

A DNS lookup asks public resolvers for the records associated with a hostname. MX records describe where mail is accepted, TXT records carry policies such as SPF and DMARC, and CNAME records create aliases for other hostnames. The answer includes more than the value: record type, name, TTL, resolver behavior, and delegation all influence what clients observe. A local zone editor view is not always the same as the public answer.

Start with the exact domain used by the envelope-from address, not only the visible From address. Query TXT records from the public internet and confirm there is one SPF policy, the expected provider includes are present, and the lookup count remains within SPF's limit. For DMARC, query the _dmarc label and check policy syntax, reporting destinations, and alignment. Compare answers from more than one resolver when a change is still propagating.

Receivers evaluate the DNS state reachable from their own networks, caches, and validating resolvers. Corporate split-horizon records, stale local caches, and a typo in the record name can make a configuration appear correct to its owner while failing everywhere else. A browser-based sandbox provides a quick public check without requiring a local DNS tool, but production monitoring should also track TTLs, delegation, and unexpected record removal.