How to use this
- Run a comparison before the planned DNS change.
- Apply the change at the authoritative provider.
- Repeat and compare answer sets and remaining TTLs.
- Wait for the old TTL before treating a cached answer as a fault.
Caching, TTL values, propagation delays, split DNS, filtering, DNSSEC handling and resolver location can produce different answers. The health scan checks public record publishing only: it does not query every authoritative server, fully validate SPF/DKIM/DMARC syntax, retrieve MTA-STS or BIMI files, test SMTP delivery, check reputation lists or prove that all users see the same records.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
Publishing and cache evidence
Compare answers, TTLs and DNSSEC validation from independent public resolvers, then use the published nameserver delegation to follow up with the authoritative provider.