Privacy Lookup

The Privacy Lookup is a free tool that queries a domain's public RDAP registration record and checks whether the registrant's real contact details — name, email, phone number, and address — are publicly exposed or hidden behind registry redaction or a privacy service. Instead of manually reading through a raw RDAP or WHOIS record and trying to judge whether what you're seeing is a real person's information or a provider's placeholder, you get a clear, direct answer: exposed or protected.

It exists because WHOIS privacy status isn't always obvious, and it matters for real reasons — checking whether your own domain's registration accidentally exposes your personal contact details, verifying a privacy add-on you paid for is actually active, or researching whether a domain you're evaluating is registered by a real, identifiable party rather than an anonymous one. It works on any public domain, which makes it useful both for managing your own registrations and for due diligence on someone else's.

When you submit a domain, the tool queries its public RDAP record — the modern, standardized replacement for WHOIS — and reads the registrant contact entry specifically, looking at its name, organization, email, phone number, and country fields. If those fields contain real-looking personal or organizational details, the domain is flagged as exposed; if they're empty, generic, or clearly attributable to a known privacy or proxy provider rather than an individual, it's reported as protected.

This reflects the live RDAP record at the moment you run the check, which is the same data source registrars and registries themselves expose publicly. Not every country-code TLD follows the same disclosure rules as the major gTLDs, and some registries redact by default regardless of whether the owner paid for privacy protection — so "protected" can mean either a dedicated privacy service is active or the registry itself is withholding the data as standard policy.

• Expect most registries to redact by default now. Since GDPR took effect in 2018, most gTLD registries hide registrant PII from public RDAP records automatically, with or without a paid privacy add-on.
• Treat an exposed registrant email as a spam magnet. A publicly listed email is a common scraper target, so domain owners who skip privacy protection often see a real spike in spam sent to that address.
• Don't be alarmed by a privacy provider's contact info. When a privacy service is active, the RDAP record shows the provider's details instead of the real owner's — that's expected, not a sign of a problem.
• Remember privacy protection isn't absolute. Legal processes like a UDRP dispute or a subpoena can still compel a registrar or privacy service to reveal the real registrant's details when required.