Public query
A visitor submits only the public technical value needed for a lookup.
Direct answer: Learn what WhoisRequest.org processes when you use its public domain and network lookup tools, and how to submit a privacy concern.
WhoisRequest.org is built for public domain and network queries. Do not enter passwords, private tokens, unpublished personal information or any value unrelated to the public technical question you are investigating.
Key relationships at a glance
Upstream request
The tool sends that value to the public service required to answer the question.
Operational record
The site may retain limited request details for reliability, security and abuse prevention.
The lookup methodology documents which public upstream services receive each supported input type.
Responsible-use restrictions and result limitations are stated in the terms of use.
A specific data-handling concern can be submitted through the privacy request instructions without repeating unnecessary personal information.
Data used to answer a lookup
The submitted domain, IP address, hostname or URL must be sent to the relevant public registration, DNS, TLS or HTTP service to produce an answer. Those upstream operators process the query under their own terms and policies.
Operational records
The web server may record the requester address, time, path, response status and user agent for reliability, security and abuse prevention. The public interface does not require an account and the application does not include advertising trackers or third-party analytics scripts.
Local worksheets and exports
The domain-history worksheet and monitoring-specification builder run in the browser. Their form entries are not submitted to WhoisRequest.org; they remain in the open tab until cleared or closed, unless the user deliberately copies or downloads the generated file. Result export buttons package a lookup response already returned by the server.
Result caching and indexing
Tool result responses and JSON API responses use private, no-store caching directives and are excluded from search results. Clean tool pages remain indexable, but WhoisRequest.org does not create public, indexable pages for submitted domains, addresses or URLs.
Public result data
Registration and network responses can include public contact or role information supplied by an upstream registry. A field being public does not make unlimited collection or republication appropriate. Use the minimum data necessary for a legitimate technical purpose.
Questions and requests
A privacy request should identify the relevant page or request, the approximate UTC time and the concern without repeating sensitive data unnecessarily. Contact details are listed on the contact page.