Privacy

RDAP Lookup is designed so that lookups run directly from your browser to the authoritative registration service. This page distinguishes what the application stores from what ordinary hosting logs may record, and states what other parties can observe when you use it.

Application storage

RDAP Lookup does not maintain a search-history database. It has no user accounts, no cookies used for tracking, and no application-level record of the resources you query. Results are fetched live and displayed in your browser.

The site is delivered as static files. It does not run a backend that receives your queries.

Query URLs and your browser

Lookups travel as URLs such as:

/lookup?q=example.com

Your browser may keep these URLs in its history, and any bookmarks or shared links will contain the query. Use a private browsing window if you want to avoid leaving the query in your local history.

Hosting and infrastructure logs

Because queries appear in URLs, the static host and any content-delivery or infrastructure layers may record them in ordinary web-server logs, along with your IP address, user agent, and referral information. The site does not maintain a search-history database, but hosting logs are outside its control.

What other parties can see

Running a lookup means your browser contacts two kinds of third parties:

• IANA, while the bootstrap registries are loaded. This reveals only that the client fetched the public registry files.
• The authoritative RDAP service, which receives your query and your IP address. That service may keep its own logs and apply its own access, rate, and privacy policies.

The service you query is selected by IANA’s registry for the resource you entered, not by this site.

Availability limits

Some authoritative services do not permit browser cross-origin requests, so those lookups cannot succeed from a static client alone. The site shows an error in that case rather than routing the query through a hidden intermediary.