Registration Data and RDAP Policy

Enterprise IT maintains registration records to administer managed domains, support DNS operation, and address security and compliance. This policy explains collection, public lookup, correction, and requests for non-public information.

The Privacy Policy governs personal-data handling. The sponsoring registrar remains responsible for the information it collects directly and for communicating its own notice.

The registrar must submit the accurate identity, contact, authority, and technical information required for the transaction and namespace. The registrant must maintain a reachable contact and respond to reasonable verification requests.

Information may include the domain, registrant or organisation details, sponsoring registrar, nameservers, status, dates, and transaction history. Additional eligibility evidence may be required under AUP Section 3. Do not substitute invented data for a privacy arrangement.

The WHOIS Lookup service presents available operational data. Missing fields, redaction, or a service error must not be interpreted as proof that a name is available for registration.

Use lookup for registration verification, technical operation, security investigation, or another lawful purpose. Do not use it for unsolicited marketing, harassment, identity profiling, or attempts to reconstruct redacted data.

Requests may be rate-limited or blocked to protect privacy and availability. Do not bypass controls by rotating identities or distributing queries. Bulk access or an integration requires an expressly agreed interface and conditions.

Ask the sponsoring registrar to correct inaccurate registration information. Include the domain and the field concerned, and supply the evidence needed to verify your authority.

Suspected deliberately false records or misuse can be raised through Report Abuse. The registry may request verification or apply proportionate restrictions if material inaccuracies remain unresolved.

Contact the compliance desk with:

• Your identity, organisation, and authority to act.
• The exact domain, requested fields, and relevant time period.
• The purpose, lawful basis, and supporting facts or legal instrument.
• Why the information is necessary and how you will protect and use it.
• A secure contact method and any genuine urgency.

Each request is assessed individually. Disclosure may be limited, refused, or redirected to the registrar. A subpoena, assertion of rights, or professional title is not automatically sufficient without verification of its effect and scope.

The registry considers legal duties, necessity, proportionality, potential harm, and affected persons’ rights. It may request clarification, redact unrelated information, or use a secure delivery channel.

Requests and disclosures are recorded for accountability. Notice to an affected person is given where appropriate and permitted; investigations or legal restrictions may prevent it. Recipients must not use disclosed information beyond the lawful purpose.

Registration records, disclosure requests, and audit information are retained according to the criteria in the Privacy Policy, including applicable legal holds. Publication in a lookup response does not create unrestricted reuse rights.

For a data-rights complaint, use the privacy contact. For a registry action or entitlement dispute, follow the Dispute Resolution Policy.