Privacy and query data

Data we record

Recording a query is part of operating the service. A query may create one or several domain records depending on the mode you choose.

• The domain or seed you submit, query mode, batch identifier, and request size.
• Status, result reason, registration date or year, data source, cache state, and response duration.
• A one-way hash of the network address, User-Agent, referring page path, and timestamps.
• Email, related domain, and message content that you voluntarily send through feedback.

How we use the data

We use this data to provide the lookup service and evaluate result quality. We do not use it to pre-register names you search for.

• Run, queue, and complete domain availability checks.
• Diagnose failures, slow lookups, cache behavior, and registry coverage gaps.
• Apply rate limits, identify repeated requests, and prevent abuse.
• Build aggregate product and performance metrics that improve defaults, ranking, and UX.

Caching and freshness

Different statuses use different short cache windows to reduce registry load and improve response time. The site and API may return cached results while retaining cache layer, source, and timing information.

Data sharing

We do not sell domain query data or provide search lists to registrars for marketing or pre-registration.

The domain must be sent to the necessary RDAP, WHOIS, or other registry service to complete a lookup. Registrar links are governed by the registrar's own privacy policy.

Retention and deletion

Raw records are retained only while needed for service reliability, abuse prevention, and aggregate product analysis. Records that are no longer needed may be deleted or aggregated. Backups and security logs may follow separate schedules.

Your choices

Use Feedback at the top of the page and choose “Privacy / data request” to ask about or request deletion of query records. Include the approximate time and query; we may need to verify the request.

Queries are sent to public registry services. Do not submit confidential names, personal information, or access credentials as query content.

Security

We use access controls, input validation, rate limiting, and one-way hashing to reduce risk, but no internet service can guarantee absolute security.

Policy changes

We will update this page and its date when our data handling changes materially.

Contact

For privacy, access, or deletion requests, use Feedback and choose “Privacy / data request.”