RDAP lookup egress environment
WHOIS, the modern way: domain, IP, or AS number in, the official registry's structured answer out — asked directly from your browser, with the registry named before anything is sent.
Nothing leaves your browser until you press Ask. Typing only computes, locally, which registry would answer.
Registry routing is deterministic: it walks vendored snapshots of the four IANA RDAP bootstrap files (RFC 9224), vendored 2026-07-08; the dns table's own publication stamp is 2026-07-06. The live answer, by design, is not deterministic — that is why this tool lives in the green room.
RDAP is WHOIS rebuilt on HTTPS and JSON (RFCs 7480, 9082, 9083): the same registry data, structured, with consistent field names and honest redaction notices instead of free-form text. This tool resolves which registry is authoritative using vendored snapshots of IANA's bootstrap files (RFC 9224), builds the exact query URL, shows it, and only sends it when you press Ask — directly from your browser to the registry, never through ronutz.com.
The deterministic layers (input classification, IDN punycode conversion, bootstrap routing, URL construction, response parsing) are golden-vector-tested like every tool on the main site. The one thing that cannot be pinned is the registry's live answer — which is exactly why this tool lives here and not at /tools.
Sources: RFC 7480 · RFC 9082 · RFC 9083 · RFC 9224 (IANA bootstrap) · data.iana.org/rdap (2026-07-08)