Registrant details, and who can see them

Registrant details, and who can see them

A domain must have a registrant record with real contact details. For generic domains like .com, that record includes name, postal address, phone and email, and it is the legal proof of who controls the name. What the public sees is limited: core domain data are always visible, while personal details are usually redacted or masked by a privacy/proxy service, and .uk domains have their own publication rules.

This picks up from a domain you can already manage at your registrar, and an account email you can access.

Before you start

• Know which rule set your domain follows. gTLDs (for example .com, .net) follow ICANN’s Registration Data Policy. .uk domains follow Nominet’s policies. Other country-code domains have their own rules.
• Decide who should legally hold the name. If you enter a Registrant Organization value for a gTLD and agree to publish it, that organisation becomes the Registered Name Holder on record. That sets who has the contractual rights to the domain.
• Have a permanent email and phone number ready. Using a colleague’s inbox, a vendor’s address or a number you do not control risks losing access. If you miss an accuracy check, registrars must suspend or cancel the name.
• Expect a lock after ownership changes. For gTLDs, a Change of Registrant can trigger a 60‑day inter‑registrar transfer lock unless you opt out beforehand. Plan any transfer around that window.
• Understand what “privacy” means. gTLD personal data are often redacted in public output. You can also add a privacy/proxy service that shows proxy details instead. Some country-code domains restrict privacy/proxy, such as .US.
• WHOIS has been replaced. For gTLDs, RDAP is the definitive public interface. .UK also provides RDAP. Port‑43 WHOIS may persist in places, but RDAP is the thing to check.

Step 1: Map your domain to the right rules

First identify the namespace. This sets what must be collected, what can be published, and how disputes or changes work.

• gTLDs (e.g. .com, .org, .net): ICANN policy applies. Registrars must collect registrant contact data and follow publication and redaction rules in RDAP. The Registered Name Holder is the party with contractual rights under the registrar agreement.
• .uk: Nominet policy applies. The registrant on Nominet’s register is the person or organisation with the contract who therefore controls the domain. Publication is limited by default.
• Other ccTLDs: Each has its own policy. Some prohibit privacy/proxy and impose strict publication. If you are unsure, check your registry’s policy notes before you choose how to present your data.

Step 2: Choose who the Registered Name Holder will be

Decide if the owner of record is an individual or an organisation. This is not cosmetic. It governs who can authorise transfers, respond to disputes and instruct the registrar.

• gTLDs: If you provide a Registrant Organization, your registrar must tell you that this value will be considered the Registered Name Holder. If you agree to publish it, it may appear in RDAP. Use the real legal entity name if you want a business to hold the rights.
• .uk: The registrant as recorded by Nominet holds control. Make sure the record matches the real controller of the name.

Avoid putting a web designer, contractor or ex‑employee in the registrant fields. That makes them the controlling party on paper. Fixing that later is a formal change of registrant, not a minor edit.

Step 3: Gather the required registrant data

For gTLDs, your registrar must collect these elements for the registrant record:

• Registrant Name
• Street
• City
• State/Province
• Postal Code
• Country
• Phone
• Email

Provide accurate details you can maintain. Under ICANN’s accuracy rules, if you knowingly give false data, fail to correct it within seven days, or do not respond to an accuracy inquiry within 15 days, the registrar must suspend or cancel the domain. Registrars also send annual registration‑data reminders showing what they hold, and they warn that false data can lead to cancellation.

For .uk, Nominet also enforces data quality. If they or your registrar cannot validate the name or address, the domain enters a “data quality” suspension that stops it working and blocks transfers until validation passes.

Step 4: Check and update your registrant record at your registrar

Sign in to your domain registrar. Review the registrant contact. Correct any outdated address, phone or email. Set the Registrant Organization if a company should be the owner of record. Confirm that the registrant email is an inbox you can access today and will still control next year.

Modern ICANN policy focuses on the Registered Name Holder data. Old “administrative contact” entries collected in the past can be removed by the registrar under the current policy set. Do not rely on an admin contact to recover control. Keep the registrant details correct.

If a suspension has taken your site or email offline at Hostworld, open a support ticket. We will help you confirm DNS and hosting once your registrar or Nominet has lifted the lock.

Step 5: Choose your publication posture: redaction or privacy/proxy

There are two layers to what the public sees.

• Redaction under ICANN’s Registration Data Policy (gTLDs): Personal registrant data in RDAP output are subject to redaction. When applied, the field is shown as “REDACTED”. Even with redaction, the registrar must provide a way to contact the registrant, either a web form that relays the message or an anonymised email address.
• Privacy/proxy services (gTLDs): If you add a privacy or proxy service, the public record shows the privacy/proxy provider’s details instead of yours. It may include a pseudonymised email for contact. Your registrar still holds your true data and must have it accurate. ICANN is implementing an accreditation programme for these services.
• Limits in some ccTLDs: Some country codes restrict or ban privacy/proxy. .US, for example, has required accurate registration data to be available and has historically disallowed proxy masking. Check your TLD’s policy if you rely on proxy services.

Privacy and redaction do not make you invisible to lawful processes. UDRP providers and others can file complaints against an unknown respondent and obtain registrant contact details through established channels. ICANN policies also include timelines for urgent lawful disclosure requests.

Step 6: Understand what is always public

RDAP output always includes core domain and registrar data for gTLDs. Expect to see:

• Domain name
• Registrar name and IANA ID
• Registrar URL and abuse contact
• Creation date, expiry date and last update
• EPP status codes
• Nameservers and DNSSEC information, if collected

Personal fields that would identify a person are usually redacted in line with policy. Where a value is redacted, RDAP shows that it is “REDACTED”.

For .uk, Nominet publishes limited data by default. The public lookup shows domain data, registrar and status. Registrant name or address are not displayed by default after GDPR changes. In some contexts, limited registrant‑related information, such as registrant type or a company number, can appear. Nominet provides RDAP as the modern interface and still offers port‑43 WHOIS for some purposes.

To confirm what is visible for your domain, run an RDAP lookup using your registrar’s tool or your registry’s RDAP client. Check that the contact route shown for the registrant works. Expect to see an anonymised address or a web form if your data are redacted or proxied.

Step 7: Keep control by staying accurate and responsive

Accuracy obligations have teeth.

• gTLDs: If you knowingly provide inaccurate data, do not update within seven days of a change, or fail to respond to an accuracy inquiry within 15 days, your registrar must suspend or cancel the domain. Non‑response beyond 15 days requires registrar action, which can include a clientHold status that stops DNS from working.
• .uk: Nominet runs an active data‑quality process. If your details cannot be validated, they send notifications and can apply a “data quality lock” that suspends the domain and blocks transfers. You can correct details through Nominet’s Registrant portal and lift the lock once validation passes.

Wrong details can therefore cost you the domain or take your website and email offline. Keep your record current and monitor the registrant inbox for accuracy checks and policy reminders. ICANN’s updated Registration Data Reminder Policy requires registrars to present your stored data annually with a reminder that false data are grounds for cancellation.

Step 8: Handle ownership changes properly

Changing who holds the rights is a formal process.

• gTLDs: A Change of Registrant is governed by ICANN’s Transfer Policy. After the change, registrars usually apply a 60‑day inter‑registrar transfer lock unless you opt out in advance. If you intend to move the domain to a new registrar soon after changing the holder, opt out before the change or accept the wait.
• .uk: A registrant change is a specific Nominet process and carries a fee. Use the proper transfer‑of‑ownership route rather than trying to re‑key details informally. Keep evidence of consent and completion.

Plan changes so they do not collide with launches, renewals or DNS moves. If a planned change affects services you run with us, tell us in advance so we can help you avoid downtime. Open a support ticket with the dates and the domain.

Step 9: Tie registration to what you run at Hostworld

Your registration data and DNS state are separate things, but they meet in public RDAP output. Nameservers and DNSSEC may be shown even when personal data are redacted. If you plan to host with us, you will point the domain at our nameservers at your registrar:

• ns1.serverworld.uk
• ns2.serverworld.uk
• ns3.serverworld.uk
• ns4.serverworld.uk

Make sure the registrant email remains valid. If a suspension lands because you missed an accuracy check, your website and mail on Hostworld will stop answering until the registrar or Nominet clears it. If that happens, we will help you confirm your DNS and hosting once the domain is restored. Open a support ticket and include the domain and any notices you received.

What next

If your goal is to bring a site online with us, your next job is to configure DNS and hosting. Start with a server you can manage and a domain whose registrant record is in order.

• Looking for a virtual server to host on? See our UK range at London VPS.
• If you are building out services, browse our VPS guides for practical next steps.
• If you need help aligning your domain with our hosting, open a support ticket.

Next in this playbook: point your domain at the correct nameservers and confirm RDAP shows the right DNS and contact route.