Evidence with boundaries.

Requests are normalized and resolved before execution. Private and reserved destinations are rejected, and redirect destinations are validated again before a supported tool follows them.

• DNS and WHOIS checks query public infrastructure.
• Web checks fetch bounded public responses with time and size limits.
• TLS checks inspect the certificate and protocol behavior presented publicly.
• Tool failures remain isolated so one unavailable signal does not invalidate the rest of a scan.

A summary prioritizes selected findings from a time-bounded scan. Results can differ across resolvers, networks, edge locations, caches, providers, and time.

• Scores organize investigation; they are not certifications or warranties.
• Absence of a public finding does not prove absence of a private vulnerability.
• Deliverability and indexation require provider-owned evidence in addition to public configuration.
• Consequential changes should be verified with the responsible provider or system owner.

Public scan summaries are cached for a limited period and only higher-coverage summaries are eligible for search indexing. Hidden scans and shared snapshots are excluded from indexing.

• Sitemap inclusion is limited by freshness, quality, popularity, and configured scope.
• Expired or incomplete summaries are not treated as indexable reports.
• Public results can be refreshed as infrastructure changes.
• Report reproducible errors through the contact page so the parser or explanation can be corrected.