WHOIS is the long-established way to inspect the public record behind a domain name. A lookup can identify the registrar, registration and expiry dates, authoritative nameservers and registry status codes. It is useful before a purchase, renewal, transfer or DNS investigation. It does not normally reveal a private person’s name, address or email today: privacy rules and registry policy often redact those details. For many generic top-level domains, the same underlying registration data is now delivered through RDAP, the structured successor to traditional WHOIS.
What WHOIS actually is
A domain is recorded in a registry for its top-level domain, such as .com, .eu or .bg. A registrar sells and manages the registration for its customer. WHOIS began as a text-based query and response protocol for looking up those records. The term is also used more loosely for web forms that retrieve registration data, even when the service behind the form uses RDAP instead.
WHOIS versus RDAP
Traditional WHOIS usually returns free-form plain text over port 43. Labels, date formats and error messages vary between providers, which makes reliable automation difficult. RDAP—Registration Data Access Protocol—returns structured JSON over HTTPS. It supports standardised objects, internationalisation, clearer referral links, access control and more precise notices about redacted information.
ICANN’s transition for generic top-level domains made RDAP the definitive registration-data service, with the old port-43 WHOIS requirement ending in January 2025. That does not mean the familiar word “WHOIS” disappeared. People, registrars and lookup pages still use it as the recognisable name for a domain registration search. Country-code domains can follow different registry rules and implementation schedules.
How to read every important field
| Field | What it tells you | What to check |
|---|---|---|
| Domain name | The exact registered label and extension | Look for spelling, punycode and the expected TLD |
| Registrar | The company managing the registration | This is normally where the customer unlocks, renews or requests an auth code |
| Registry ID | A registry-side identifier for the domain | Useful when distinguishing similarly named records |
| Created / registration date | When the current registry record was first created | Do not treat age alone as proof of reputation or continuous ownership |
| Updated date | When a registry event last changed the record | It may reflect a renewal, transfer, contact change or nameserver update |
| Expiry date | The end shown for the current registration term | Confirm renewal status in the registrar account; registry dates can be affected by auto-renew grace rules |
| Nameservers | The authoritative DNS servers delegated at the registry | Compare them with the intended DNS provider; this does not list every DNS record |
| DNSSEC | Whether signed delegation data is present | A mismatch during a DNS move can stop resolution |
| Status codes | Locks, holds or life-cycle states | Transfer prohibitions and hold states require different action |
| Registrant, admin and technical contacts | Roles associated with the registration | Personal data may be redacted; a relay or registrar contact may be supplied |
| Abuse contact | Where to report abuse involving the registration | Use it for evidence-based abuse reports, not ordinary ownership enquiries |
Status codes and transfer-lock signals
Status codes are often the most actionable part of a lookup. They are not all errors. A normal security lock can prevent an unauthorised transfer, while a hold can remove the domain from DNS publication.
| Status | Usual meaning | Practical response |
|---|---|---|
ok | No special prohibition is reported | No status action is normally required |
clientTransferProhibited | The registrar has applied a transfer lock | Unlock it in the registrar account before an authorised transfer |
serverTransferProhibited | The registry has blocked transfer | Ask the registrar why; the customer may not be able to remove it directly |
clientUpdateProhibited | Registrar-side updates are restricted | Remove the lock only when a planned change requires it |
clientHold / serverHold | The name may be excluded from the DNS zone | Check payment, verification, abuse or registry-policy issues with the registrar |
redemptionPeriod | The deleted registration may still be restorable at extra cost | Contact the registrar immediately; normal renewal may no longer apply |
pendingDelete | Deletion is in its final stage | Recovery is usually no longer available; monitor the registry process |
For a transfer, look for clientTransferProhibited or serverTransferProhibited, but also check the registrar account. A domain can face policy or timing restrictions that one status line does not fully explain. Never disable a protective lock earlier than necessary, and enable it again after the transfer or account work is complete.
Privacy, GDPR and redacted contacts
GDPR did not make all registration data secret. Operational facts—registrar, dates, nameservers and status—usually remain available because they are needed to operate the domain system. Personal contact details can identify an individual, so registrars and registries often show “REDACTED FOR PRIVACY,” omit the value or provide an anonymised relay.
Redaction does not mean the owner is suspicious, that the name is for sale or that nobody can be contacted. A registrar may offer a web form, relay address, disclosure process or abuse channel. Legitimate requests can require a stated purpose and supporting evidence. Rules differ for legal entities, individuals and country-code registries, so do not assume that a field visible for one TLD must be visible for another.
What a lookup can and cannot prove
- It helps verify delegation and transfer locks, but cached DNS and separate registrar checks still matter.
- The expiry field supports renewal planning, but does not replace the billing state in your account.
- It cannot prove website identity or availability. Reserved and premium names may have no normal record.
- It does not show hosting location. DNS may point to a server, CDN or proxy.
When to use the lookup tool instead of this guide
Use this article when you need to understand terminology, privacy and status codes. Use EuroVDC’s live WHOIS lookup tool when you have a specific domain to inspect. It is the practical step before a transfer, when checking an expiry warning, or when confirming that a nameserver change reached the registry. If the response says no registration record was found, confirm availability on domain search; absence from WHOIS or RDAP alone is not a purchase guarantee.
If delegation is correct but the site still fails, continue with DNS-record, DNSSEC, web-server and TLS checks. WHOIS is a starting point, not a complete website diagnostic.
A safe pre-transfer checklist
- Confirm that you control the registrar account and that its email and multi-factor authentication are current.
- Check the registrar name, expiry date and all status codes in the live record.
- Make sure the domain is not on hold and resolve any verification or billing issue first.
- Unlock the transfer only when ready, then request the authorisation code through the registrar.
- Record the current nameservers and DNS zone before moving anything.
- After completion, verify the registrant account, nameservers, DNSSEC and renewal settings, then restore the transfer lock.
Common myths that waste time
- “An old creation date guarantees SEO authority.” Search performance depends on content, links, relevance and technical quality, not a WHOIS birthday alone.
- “Changing the registrant moves the website.” Registration, DNS and hosting are separate. Contact changes do not copy files or databases.
- “The WHOIS email always reaches the owner.” It can be redacted, relayed or outdated. Use the registrar’s documented contact route.
- “The expiry date is the exact moment anyone can register the name.” Grace, redemption and deletion phases can continue after expiry.
EuroVDC provides domain and infrastructure services from Sofia, Bulgaria, in the EU. Registry policy—not server location—determines which WHOIS or RDAP fields are disclosed.
Frequently asked questions
Is WHOIS still public after GDPR?
Yes, core operational data is generally public. Personal registrant, administrative and technical contact values are often redacted or replaced by a relay under the applicable policy.
What is the main difference between WHOIS and RDAP?
WHOIS is usually free-form text from a legacy protocol. RDAP supplies structured JSON over HTTPS, with standard events, links and clearer support for access and redaction rules.
Does an expiry date mean the domain will be free that day?
No. Auto-renew grace, redemption and pending-delete stages may follow. The exact life cycle depends on the registry and registrar.
Can I identify the owner of a .eu or .bg domain?
You may see registrar and technical data, but personal contacts can be hidden under GDPR and local registry policy. Use the registry or registrar’s legitimate contact or disclosure process.
Does WHOIS show the web host?
Not reliably. It shows registration and delegated nameservers. DNS records may point to a hosting server, CDN or proxy and require separate investigation.
Why do new nameservers not appear immediately?
The registrar must publish the delegation to the registry. After that, resolver caches may still retain older DNS data until its TTL expires.
Agent tip: EuroVDC publishes service discovery information in llms.txt and the for-agents guide. These machine-readable resources help software find documented tools and catalog links; they are not an SEO ranking shortcut or guarantee.




