Validated input
The lookup normalizes a domain, address, hostname or URL before contacting an upstream service.
Direct answer: See how WhoisRequest.org validates inputs, selects WHOIS, RDAP, DNS and HTTP sources, limits requests, records time and states uncertainty.
Every result is a time-stamped observation produced from a validated public input. The method changes by protocol, but source selection, bounded requests and explicit uncertainty are consistent across the site.
Key relationships at a glance
Named source
The protocol selects the registry, RIR, DNS resolver or public website endpoint used for the observation.
Bounded conclusion
The result records what was observed, when it was observed and what the observation cannot prove.
The RDAP lookup demonstrates source-aware registration routing and retains typed events and notices.
For a multi-record resolver snapshot, use the DNS report and then verify material findings against the relevant authority.
For automated requests, the JSON lookup API reference maps each tool identifier to its input, response model and error behavior.
Input normalization
Domain inputs are separated from URLs, lowercased, trimmed, validated label by label, and converted to their ASCII IDNA form when necessary. IP tools require a literal IPv4 or IPv6 address. Website tools accept only public HTTP or HTTPS destinations without embedded credentials.
Registration-data routing
Legacy WHOIS begins with IANA and follows a usable registry referral. When IANA publishes no port-43 server, the lookup falls back transparently to RDAP. RDAP responses retain typed events, entity roles, notices and source links instead of flattening them into an owner-and-date table.
DNS and website observations
DNS record families are queried independently so an address failure does not hide mail or authority evidence. Website requests are bounded, do not execute page scripts, and distinguish HTTP status, redirects, TLS details and timing. Private, loopback, link-local, multicast and reserved destinations are blocked.
Interpretation and reproducibility
The page keeps the normalized query, source and UTC check time with the output. A single observation can change immediately and can differ by resolver, route, cache, region or provider. Consequential decisions should be verified with the responsible registry, registrar, RIR or service operator.
Practical standard
- Validate before requesting
- Use the protocol's authoritative routing mechanism
- Cap response size and request time
- Keep raw or structured source context
- State what the result does not prove