Direct answer: Send a GET request with the tool identifier and lookup value in the path; the API returns source-aware JSON or a specific 400, 404 or 422 error.
Place the tool identifier and domain in the request path:
GET /api/v1/lookup/rdap/example.comUse an HTTP GET request and keep the lookup value in the path. No API key is currently required for this public endpoint. Test the same domain in the interactive RDAP lookup when you need to compare the JSON fields with their visible interpretation.
curl 'https://whoisrequest.org/api/v1/lookup/rdap/example.com'Simple domains, hostnames, IP addresses and AS numbers remain readable in the path. The interactive forms safely encode values that contain reserved path characters. The endpoint returns JSON for both successful lookups and documented errors.
A successful response contains the selected tool identity, a data object produced by that lookup and a methodology URL. Fields inside data vary by protocol because a DNS answer, an RDAP object and an HTTP observation do not describe the same evidence. Read the lookup methodology before combining those evidence layers in an automated workflow.
{
"data": { "query": "example.com", "checked_at": "..." },
"methodology": "https://whoisrequest.org/methodology",
"tool": {
"id": "rdap",
"name": "RDAP Lookup",
"url": "https://whoisrequest.org/rdap"
}
}Choose the identifier that matches the question being asked. Do not treat outputs from one evidence layer as a substitute for another.
whoisInput: Domain name
Returns the normalized query, responding WHOIS server, parsed fields, preserved raw text and UTC observation time. Referral behavior remains visible in the source rather than being presented as a universal owner record.
rdapInput: Domain or IP address
Returns the selected RDAP source URL, a compact summary, typed events, nameservers, notices, raw JSON and UTC observation time. Consumers should keep event actions and notices attached to their values.
whois-ipInput: IPv4 or IPv6 address
Accepts a literal public IP address and returns the RDAP network source, containing range details, events, notices and raw response. The registered range can be broader than the queried address.
domain-availabilityInput: Domain name
Returns a cautious conclusion assembled from registration and DNS evidence, plus separate registered and has_dns indicators. An inconclusive or negative public lookup is never converted into a purchase guarantee.
dnsInput: Domain name
Returns resolver-visible records grouped by type, with errors, warnings and a UTC query time. Negative and partial answers remain separate so clients can distinguish missing data from a failed lookup.
dns-reportInput: Domain name
Queries the report's fixed DNS record families and returns each observed set together with record-specific errors and diagnostic warnings. The report is a resolver view, not an authoritative zone transfer.
dnssec-checkInput: Domain name
Returns parent DS data, child DNSKEY data, matching key-tag and digest evidence, plus warnings for absent or inconsistent chain material. It does not replace validation by a recursive resolver.
nameserverInput: Domain name
Returns the domain's observed NS hostnames and the IPv4 or IPv6 addresses resolved for each hostname. Address failures are retained per nameserver instead of hiding a partially usable delegation.
reverse-dnsInput: IPv4 or IPv6 address
Accepts a public IP address and returns its PTR-derived hostname, aliases and UTC observation time. A missing PTR is represented as a lookup outcome rather than a forward-DNS result.
asn-lookupInput: IPv4 or IPv6 address
Returns the queried address with the ASN, organization, ISP, country and network context supplied by the lookup source. These are routing or registration attributes, not device geolocation.
uptimeInput: Public website URL
Returns the final HTTP status, reason, elapsed milliseconds, redirect location, server header and probe time for one bounded request. It does not aggregate regions or historical availability.
ssl-checkInput: Public hostname
Returns certificate subject, issuer, validity window, covered DNS names and negotiated cipher for the inspected host. The response reflects the certificate presented to this connection.
http-headersInput: Public website URL
Returns the HTTP status and a bounded set of response headers, with notes for observable caching and browser-policy signals. Page scripts are not executed and rendered DOM state is outside the response.
idn-converterInput: Domain name
Returns the submitted value beside normalized Unicode and ASCII forms. The endpoint converts labels only; it does not register, resolve or judge whether visually similar names are safe.
A missing or malformed lookup value is a client error, an unknown identifier is not found, and a validated lookup that cannot complete returns an unprocessable response.
| Status | When it is returned | Response key |
|---|---|---|
| 400 | The lookup value is missing or malformed. | missing_query or invalid_query |
| 404 | The path contains an unknown tool identifier. | unknown_tool |
| 422 | Validation fails or the selected upstream lookup cannot complete. | lookup_failed |
The public endpoint is intended for occasional interactive use and has no uptime or bulk-throughput service-level promise. Cache stable results only for a duration appropriate to their source, retain timestamps and source references, and query the authoritative registry, RIR or DNS service directly for production-scale integrations. A cached registration record is not evidence of the current state after its observation time.
This is a server-side API: WhoisRequest.org validates the input and sends the normalized query to the upstream registry, RIR, DNS resolver or website required by the selected tool. API responses use private, no-store caching directives and are excluded from search indexing, but the relevant upstream service still receives the technical query. Do not submit credentials, private URLs or unrelated personal information. Review the lookup privacy policy before integrating sensitive workflows.