The day WHOIS went dark
Before 25 May 2018, a WHOIS lookup on almost any domain read like a business card. Type in a name and you got the owner's name, street address, phone number, and email — published by default, free for anyone to read, and scraped at industrial scale by spammers, marketers, and anyone else who wanted it.
Then the European Union's General Data Protection Regulation (GDPR) took effect, and the public internet lost its phone book overnight. On 17 May 2018, eight days before GDPR's enforcement date, ICANN adopted its Temporary Specification for gTLD Registration Data, ordering registries and registrars to stop publishing registrants' personal data. Within weeks, "REDACTED FOR PRIVACY" replaced real names and addresses across the domain system.
Eight years later, the change is permanent. ICANN's Registration Data Policy, which took effect on 21 August 2025, keeps the same redaction in place. This post explains what a WHOIS lookup still shows in 2026, what went dark and why, and the three legitimate ways to reach the data that is no longer public.
What changed: before and after GDPR
The rule is simple to state and easy to misunderstand. Registrars still collect exactly the same registration data they always did — your name, address, phone, and email are still on file, still escrowed, still handed to dispute providers when a complaint is filed. What changed is publication. The public record was split in two: operational facts about the domain stayed visible; personal facts about the human behind it went dark.
WHOIS field | Before 25 May 2018 | After GDPR (2026) |
|---|---|---|
Registrant name | Published in full | Redacted — "REDACTED FOR PRIVACY" unless the registrant consents to publish |
Registrant street, city, postal code | Published in full | Redacted |
Registrant email | Published in full | Redacted, or replaced with an anonymized forwarding address or web form |
Registrant phone and fax | Published in full | Redacted |
Admin and tech contacts | Published in full | Redacted on the same basis as the registrant |
Sponsoring registrar | Published | Still published — unchanged |
Creation and expiry dates | Published | Still published — unchanged |
Domain status codes | Published | Still published — unchanged |
Name servers | Published | Still published — unchanged |
Two details matter most. First, redaction is not something you switch on, and nobody can charge you for it — it is applied by the registry or registrar as a matter of policy, whether or not you bought WHOIS privacy. Second, the redacted email is often not a dead end: many registrars replace it with a per-domain forwarding address or a web form, so a stranger can still reach the owner without ever seeing the owner's real address.
Why GDPR forced ICANN's hand
GDPR made it illegal to publish someone's personal data without a lawful basis, and the old WHOIS model had none that would survive scrutiny — a public, globally searchable database of names, home addresses, and phone numbers, published by default with no consent and no opt-out, with fines of up to €20 million or 4% of global annual turnover behind it.
The practical problem was that a registrar cannot reliably know in advance whether a given registrant is an EU resident. So most registrars did the only safe thing: they redacted all gTLD registrant data globally, not just for European customers. That is why a lookup on a domain registered in Texas by an American owner shows the same redaction as one registered in Berlin.
The redaction covers generic top-level domains — .com, .net, .org, and the rest — because those are the ones ICANN's contracts govern. Country-code domains (.uk, .de, .fr, and the rest) are not covered by ICANN's gTLD rules at all. Each ccTLD registry sets its own policy, and several of them were already hiding personal data before 2018.
What you can still see in 2026
Redaction did not kill WHOIS lookups — it narrowed them. A lookup on any gTLD today still answers the questions most people actually ask:
- Is the domain registered, and until when? Creation and expiry dates remain public, so you can tell whether a name is about to drop.
- Who is the registrar? The sponsoring registrar is named, which tells you exactly who to contact with a disclosure request or a dispute.
- What is the domain's status? Status codes such as clientTransferProhibited or pendingDelete tell you whether the name is locked, in a grace period, or on its way out.
- Where does it point? Name servers are still published, so you can see the DNS setup and hosting infrastructure.
What you cannot do any more is identify the human being who owns a domain from the public record alone. For that, you now need one of the three routes below. If you want to see exactly what a modern lookup returns, run the name through Nomlen's free WHOIS checker — it shows the live record, redactions included.
RDAP replaced WHOIS — and most people didn't notice
While the redaction debate dominated the headlines, the protocol underneath was quietly replaced. RDAP, the Registration Data Access Protocol, is the structured, JSON-over-HTTPS successor to the plain-text WHOIS protocol, and ICANN now requires gTLD registries and registrars to run it. As of 28 January 2025, ICANN removed the requirement for gTLD registrars — and most gTLD registries — to run a WHOIS service at all. The registries for .com, .name, and .post are the remaining exceptions still required to provide WHOIS.
For an ordinary user, nothing visibly changes: you type a domain into a lookup tool and get the same redacted record back either way. RDAP's real importance is that it was designed for tiered access — different data for different authenticated users — which is what makes the disclosure routes in the next section possible. We compared the two protocols in detail in our RDAP vs WHOIS guide.
The three legal ways to get the hidden data
The data is not gone — it is gated. If you have a legitimate reason to see it, there are three routes, in order of effort:
1. Use the anonymized contact on the record
Many registrars replace the registrant's email with a per-domain forwarding address or a web form. Send your message there and the owner can reply without revealing anything. This is the fastest route for a simple question — "Is this domain for sale?" — and the only route that needs no justification at all. Expect a low reply rate: owners of valuable names ignore most inbound mail.
2. Ask the registrar directly
Every registrar must have a process for disclosing redacted data to a third party with a legitimate interest — the legal hook is GDPR Article 6(1)(f), which permits processing where it is necessary for a legitimate interest not overridden by the data subject's rights. In practice you write to the registrar, state who you are, and explain why you need the data: a trademark you own, a phishing site impersonating your company, a court order. The registrar makes its own legal assessment and decides. There is no fixed deadline and no guarantee — and each registrar applies its own threshold, so the same request can succeed at one registrar and fail at another.
3. File through ICANN's Registration Data Request Service (RDRS)
The standardized route is RDRS, a free service ICANN launched on 28 November 2023. Instead of guessing each registrar's request form, you submit one standardized disclosure request through a single system, and RDRS routes it to the registrar of record. The service was launched as a two-year pilot to measure real demand and inform the long-debated System for Standardized Access/Disclosure (SSAD) policy recommendations. The pilot ended in November 2025, and on 30 October 2025 ICANN's Board confirmed RDRS will keep running until December 2027 while the community decides what a permanent system looks like.
What RDRS does — and does not do — is important to understand. It standardizes the front door, not the outcome. Each registrar still applies its own legal assessment to every request; RDRS does not harmonize the legal threshold, and it does not grant automatic access. It is also voluntary for registrars. At launch, 56 registrars participated, covering just over half of all gTLD domains. By September 2025 participation had grown to 79 registrars, but coverage still sat slightly under 50% of gTLD domains under management — so roughly half of all gTLD names cannot be reached through RDRS at all, and requests for those names have to go direct to the registrar.
RDRS at a glance (as of October 2025) | Figure |
|---|---|
Launched | 28 November 2023 |
Cost to requesters | Free |
Participating registrars at launch | 56 |
Participating registrars (September 2025) | 79 |
Share of gTLD domains covered | Slightly under 50% |
Unique requester accounts | About 13,000 |
Domain searches conducted | About 39,000 |
Disclosure requests closed | About 3,300 |
Extended until | December 2027 (ICANN Board decision, 30 October 2025) |
The numbers tell the real story: RDRS is a working system, but a small one. Thirteen thousand requesters and 3,300 closed requests across two years is a trickle compared with the hundreds of millions of gTLD domains in existence. Most of the people who used to look up an owner in seconds now either use the anonymized contact, or never bother. If your case is a genuine dispute, there is a fourth route that bypasses all of this — file a UDRP complaint. Once a complaint is filed, the registrar must disclose the registrant's details to the dispute provider, as our UDRP guide explains.
GDPR redaction vs WHOIS privacy: not the same thing
One of the most common questions since 2018 is whether WHOIS privacy is now pointless. It is not — but what it does has changed. Redaction hides your data from the published record. WHOIS privacy goes further: it replaces your details with a proxy identity at the registrar itself, so even a party that somehow obtains the underlying record sees the proxy, not you. Redaction is free and automatic. Privacy is a paid add-on at most registrars, and it also shields you in contexts where redaction does not reach.
GDPR redaction | WHOIS privacy (proxy service) | |
|---|---|---|
What it hides | Personal data from the public WHOIS/RDAP record | Your identity from the record entirely, replaced with a proxy |
Cost | Free — applied by policy, not a product | Usually paid (often bundled free by some registrars) |
Who applies it | Registry or registrar, automatically | You, by enabling it at the registrar |
Can a requester still reach you? | Yes — anonymized email or web form, or a disclosure request | Yes — through the proxy service, which forwards mail |
Does it protect against a UDRP disclosure? | No — registrars must disclose to dispute providers | No — the proxy reveals the underlying registrant to the provider |
For most individual owners, GDPR redaction alone is enough — your home address is not in the public record any more, and that was the real risk. If you run a business and want a layer between your identity and every requester, privacy protection is still worth having. We weighed the full case in Domain Privacy Protection: Is It Worth It?
What this means for you in 2026
If you own domains: your personal data is protected by default, and you do not need to do anything to keep it that way. But check your own record — some registrars let you consent to publish your details, and some older registrations still carry that consent from before 2018. If you want to be contactable about a sale, make sure the anonymized forwarding address on your record actually reaches you.
If you are buying a domain: you can no longer verify the seller from the public record. Use the anonymized contact, or go through a marketplace or broker with escrow — never send money to an anonymous seller on the strength of a WHOIS record that shows nothing. Expiry dates are still public, so you can still watch a name you want and catch it when it drops.
If you are enforcing a trademark or fighting abuse: build your case before you ask for data. A request that names the trademark, shows the infringement, and cites a legitimate interest is far more likely to be granted than a bare "who owns this?" — and a UDRP complaint, once filed, compels disclosure to the dispute provider. For phishing or fraud, law enforcement requests are handled on an urgent track, with a defined timeline for cases involving imminent threats to life, serious bodily injury, critical infrastructure, or child exploitation.
If you are a researcher or investigator: accept that the open era is over. The public record gives you the domain's dates, registrar, status, and name servers — enough to map infrastructure and spot patterns — but the identity layer now requires a justified request, and the standardized system still stops at roughly half of all gTLD names.
The future: a permanent system, still undecided
Eight years after the Temporary Specification, the domain industry still has no permanent access system. The EPDP Phase 2 recommendations for a System for Standardized Access/Disclosure (SSAD) — 18 interdependent recommendations covering accreditation, request criteria, response requirements, logging, and auditing — remain pending, and RDRS exists to gather the evidence the ICANN Board needs before acting on them. The Board's October 2025 decision to keep RDRS running through December 2027 guarantees no gap in service while that debate continues, but it is a bridge, not a destination.
The realistic outlook for the next two years is more of the same: public redaction stays, RDRS slowly gains registrars, and the threshold for disclosure stays in each registrar's hands. WHOIS will never go back to being a public phone book — the people who adapted, using the anonymized contact, the RDRS front door, and the UDRP route when it counts, are the ones who can still find an owner when it genuinely matters.
Frequently asked questions
Can I still find out who owns a domain in 2026?
Not from the public record alone. For gTLDs, the registrant's name, address, phone, and email are redacted by default. You can still see the registrar, the creation and expiry dates, the status codes, and the name servers — and you can reach the owner through the anonymized contact on the record, a direct request to the registrar, or ICANN's RDRS.
Did GDPR delete WHOIS data?
No. Registrars still collect and retain the same registration data, and it is still escrowed and available to dispute providers and law enforcement through proper channels. GDPR changed what is published, not what is collected.
What is ICANN's Registration Data Request Service (RDRS)?
A free service launched on 28 November 2023 that lets anyone submit a standardized request for non-public gTLD registration data. It routes the request to the registrar of record, which makes its own legal decision. It was a two-year pilot, extended by the ICANN Board on 30 October 2025 to run until December 2027.
Does RDRS guarantee I will get the registrant's details?
No. RDRS standardizes how you ask, not whether the answer is yes. Each registrar applies its own legal assessment, and participation is voluntary — as of late 2025, slightly under half of all gTLD domains were covered by participating registrars.
Is WHOIS privacy still worth paying for after GDPR?
For most people, redaction alone covers the main risk — your address is no longer public. Privacy protection adds a proxy identity at the registrar, which helps if you want an extra layer between your identity and anyone who obtains the underlying record. Some registrars include it free.
What can a WHOIS lookup still show me?
The sponsoring registrar, creation and expiry dates, domain status codes, and name servers. That is enough to check whether a name is taken, when it expires, whether it is locked, and where it points.
Do country-code domains like .uk or .de follow the same rules?
No. ICANN's redaction rules cover generic TLDs only. Each ccTLD registry sets its own policy, and several were already hiding personal data before 2018. What you see depends on the registry that runs the extension.
How do I contact a domain owner if their details are redacted?
Start with the anonymized email or web form on the WHOIS/RDAP record — the registrar forwards your message without revealing the owner's real address. If that fails and you have a legitimate reason, ask the registrar directly or file a request through RDRS. For a genuine trademark dispute, filing a UDRP complaint compels disclosure to the dispute provider.




