How consensus, health, and registration data are derived

Lookups run in parallel against Google Public DNS, Cloudflare 1.1.1.1, and Quad9. For each requested record family, the app compares normalized answer sets and computes a consensus score from the most common signature.

This is intentionally labeled as a resolver-consensus view. It is not marketed as a private global probe network.

Health cards derive from visible records plus lightweight heuristics: SPF from TXT records, DMARC from the `_dmarc` subdomain, CAA from CAA records, and DKIM from a shortlist of common selectors.

DNSSEC trust is estimated from DS visibility and authenticated-data flags reported by public recursive resolvers.

RDAP bootstrap resolution uses IANA’s DNS bootstrap registry, then the app queries the authoritative RDAP service for registrar, nameserver, status, and event metadata.

For TLDs that do not publish a usable RDAP bootstrap entry, the app falls back to the authoritative WHOIS server derived from IANA so registration data remains available for domains such as `.ro`.