Data Sources

Our results are only as good as the data behind them. Here is where that data comes from.

DNS resolvers

DNS lookups and propagation comparisons use these public DNS-over-HTTPS resolvers:

• Cloudflare (1.1.1.1) — https://cloudflare-dns.com/dns-query
• Google (8.8.8.8) — https://dns.google/resolve
• Quad9 (9.9.9.9) — https://dns.quad9.net:5053/dns-query
• AdGuard DNS — https://dns.adguard-dns.com/resolve

Each resolver returns whatever is currently in its cache, subject to record TTLs. Availability and answers are controlled by the resolver operators.

RDAP / registration data

Domain, IP, and ASN registration data is retrieved via RDAP using the IANA bootstrap system, which routes each query to the authoritative registry. Contact fields are frequently redacted by registry privacy policies.

IP registration & ASN data

Network ownership, CIDR blocks, and ASN details come from Regional Internet Registries via RDAP. Country codes reflect registration, which may differ from where an address is physically used.

IP geolocation

Approximate location is shown only when a geolocation provider is configured by the operator. When none is configured, we omit location rather than guess.

HTTP responses

Header and response-time tools fetch the target directly from our server. The values reflect that single request from our network location at that moment.

Update frequency & accuracy

DNS results are near-real-time (cache-dependent). RDAP reflects the registry’s latest published record. All external data is provided under the respective providers’ terms; we cache conservatively and do not redistribute bulk datasets.