whois .com: Verisign, Registrars and Thin Records

When people search for whois .com, they usually want one simple thing: the current registration record for a .com domain, and an explanation of who holds which part of that record. In plain terms, .com sits at two levels. Verisign operates the .com registry, which holds the central registry record for all .com names. The sponsoring registrar, the company through which the name was registered, manages the customer-facing registration record and many practical changes to it.

The important modern point is that for gTLDs such as .com, RDAP is now the definitive source for registration data. That became the position on 28 January 2025, when WHOIS port 43 obligations for gTLD registries and registrars ended. People still say WHOIS, and the phrase whois .com remains common shorthand, but the authoritative place to check current gTLD registration data is now RDAP.

What whois .com means today

Today, whois .com usually means a lookup of the current registration details for a .com domain name. People use the term out of habit, but what they are really asking for is the present registry and registrar data for that name.

A .com name is part of the gTLD system. At the top level, Verisign operates the .com registry. That means it maintains the central registry database for .com names and publishes the core status data associated with those domains. Separately, registrars handle the retail side. They sponsor registrations, manage the customer account, and keep the fuller registration record attached to the domain.

This split matters because one source may show only part of the picture. A registry-level response often confirms that the domain exists, shows its status, and identifies the sponsoring registrar. The registrar-level record may hold additional detail about management of the domain, subject to policy and privacy limits.

Since 28 January 2025, RDAP has been the definitive source for gTLD registration data. So, in current practice, whois .com is best understood as a plain-language label for an RDAP-based lookup of a .com domain’s registration record, rather than a strict reference to the old WHOIS protocol.

whois .com and RDAP: what changed on 28 January 2025

The key change on 28 January 2025 was procedural and authoritative. On that date, WHOIS port 43 obligations for gTLD registries and registrars ended. For .com and other gTLDs, RDAP became the definitive source for current registration data.

That does not mean the word WHOIS vanished overnight. In practice, most users, many tools, and countless articles still use WHOIS as shorthand for a domain lookup. The habit is understandable. The search intent has not changed: people still want to know whether a domain is registered, which registrar sponsors it, what statuses apply, and when it was created or expires.

What changed is the official lookup framework. If you need the authoritative current record for a gTLD such as .com, RDAP is now the right place to check.

A practical way to think about it is this:

• WHOIS is still the common label people say
• RDAP is the definitive source for current gTLD registration data
• For .com, you may still encounter registry and registrar references, because each serves a different role

This distinction matters when you are checking ownership history, expiry posture, transfer timing, or whether a name is locked. For example, a domain usually cannot be transferred to another registrar for 60 days after registration or a registrar transfer, and the relevant status indicators are typically what users are trying to confirm in a whois .com search.

Verisign's role in .com registration data

Verisign’s role is the registry role. It operates the central .com registry, which means it maintains the authoritative registry-level record for .com domain names. That record is not the same thing as a full customer account record held by a registrar.

In practical terms, the registry record exists to keep the domain system working. It tracks the domain’s existence in the .com namespace, its key statuses, and the registrar that sponsors it. If you are checking a .com name, Verisign’s side of the picture helps answer questions such as whether the domain is active in the registry, what nameservers are delegated, and which registrar is responsible for the registration.

This is why registry and registrar lookups may appear different without being inconsistent. They are showing different layers of the same domain’s administration.

A registry-level response commonly helps you identify:

• the sponsoring registrar
• the domain’s status codes
• the nameservers on record
• the creation and expiry dates

The registrar, by contrast, handles the registrant relationship. It manages renewals, account changes, transfer processes, and much of the underlying registration data that users associate with WHOIS. So if Verisign and a registrar display different pieces of information, that usually reflects role separation, not an error. One is the central registry view. The other is the sponsoring registrar’s customer-facing view.

Why .com was known as a thin registry

Historically, .com was described as a thin registry. In plain English, that means the central registry did not hold one single, complete public contact record for every domain at registry level. Instead, the registry stored a narrower set of core data, while the sponsoring registrar held the fuller registrant and contact record.

That thin model is easy to understand if you picture the domain record in two parts. The registry held the minimum operational layer needed to run the namespace. The registrar held the richer account and contact layer tied to the customer relationship.

So, for a traditional .com lookup, the registry side might show that the name was registered and identify the sponsoring registrar. To find fuller registration details, the user would then be referred to that registrar.

This is the practical distinction:

• a thin registry record is limited and operational
• a fuller registration record sits with the registrar
• the registry does not function as a single complete public contact database for every .com domain

This also helps explain why older guidance about whois .com often told users to start at the registry response and then follow the referral to the registrar. Even before modern privacy changes, the fuller contact-level data was historically associated with the registrar layer rather than a single complete registry-level record for .com.

What a whois .com lookup typically shows

A whois .com lookup, now better thought of as an RDAP-backed lookup for current gTLD data, usually shows a practical set of fields rather than a narrative description. Most users are checking whether the domain is registered, who sponsors it, and what state it is in.

Common fields people expect to see include:

• domain status
• nameservers
• sponsoring registrar
• creation date
• expiry date
• a referral or clear indication of the sponsoring registrar

These fields are the core of everyday domain checking. They help with basic due diligence, troubleshooting, transfer planning, and expiry monitoring. If you are trying to understand where a domain sits in its life cycle, status and date fields are usually the most useful starting point.

Contact visibility is the area that changed most for ordinary users. After GDPR took effect on 25 May 2018, most registrant personal data in WHOIS became redacted. As a result, public lookups for many .com domains no longer display the direct personal contact details users once expected to see.

If the domain has expired, dates and status may also help you interpret where it is in the post-expiry process. Many gTLD names pass through an auto-renew grace period of up to 45 days, then a 30-day redemption period, then 5 days of pending delete. That is often more useful than any contact field in a modern whois .com search.

Why contact details are often redacted in whois .com

If you search whois .com records today, the main surprise is usually not what you find, but what you do not. Older guides often show owner names, street addresses, email addresses and phone numbers. For most .com domains, that is no longer what public registration data looks like.

The key change came with GDPR on 25 May 2018. After that date, most registrant personal data in WHOIS became redacted from public view. In practical terms, public records for many .com names stopped showing the individual or business contact details that older tutorials assumed would be visible.

That is why two things can both be true at once. A domain is properly registered, and the public record still reveals very little about the person or company behind it.

A few points help clear up the confusion:

• Redaction does not mean the data does not exist. It means the personal data is generally not displayed publicly.
• Older screenshots and help articles may reflect pre-GDPR WHOIS output rather than the current position.
• Some records still show technical or administrative clues, such as status codes, name servers or the sponsoring registrar, even when the registrant identity is hidden.

There is also a second, newer shift. ICANN's RDAP became the definitive source for gTLD registration data on 28 January 2025, when WHOIS port 43 obligations for gTLD registries and registrars ended. So when people say whois .com now, they often mean registration data lookup generally, not the older public WHOIS format.

How to find the sponsoring registrar for a .com domain

When you need to know who manages a .com domain, the usual goal is to identify the sponsoring registrar. That matters for transfer checks, renewal problems and abuse reporting. It is also the practical next step when the registry-level record is thin.

For .com, the registry has historically held a thin record. In plain terms, the registry-level result may confirm the domain exists and point you to the registrar, but not provide the fuller record people expect. If that happens, do not stop at the first lookup.

A simple process works well:

• Search the domain using a current registration data lookup, ideally via RDAP because ICANN's RDAP became the definitive source for gTLD registration data on 28 January 2025.
• Note the sponsoring registrar shown in the result.
• Visit that registrar's RDAP or registration data service for the domain.
• Review the registrar-level record for status, dates, contact routes and any published abuse information.

This distinction is important. The registry tells you where the name is sponsored. The registrar is often where the more useful operational detail sits.

In practice, people look up the sponsoring registrar for three common reasons:

• To check whether a recent registration or transfer may affect movement of the domain
• To resolve renewal or expiry confusion
• To find the correct channel for abuse or security reports

If the public record is sparse, that is normal. The registrar identity is often the most useful piece of information you can get.

whois .com for transfers, expiry and drop timing

A whois .com lookup is often less about ownership and more about timing. People want to know whether a name can be transferred, whether it has expired, or when it might finally drop.

For transfers, one rule catches many users out. A domain usually cannot be transferred to another registrar for 60 days after registration or a registrar transfer. So if a lookup shows a very recent creation date or a recent transfer, that can explain why a transfer request is blocked even when the registrant wants to proceed.

Expiry is also easy to misread. The expiry date in a .com record is important, but it is not the same thing as a guaranteed deletion date. After expiry, many gTLD names follow a multi-stage path before they become available again.

The common sequence is:

• Auto-renew grace period, up to 45 days
• Redemption period, 30 days
• Pending delete, 5 days

That means an expired .com is often not immediately available to re-register. It may still be renewable by the current registrant during parts of that process, depending on the registrar's handling.

For buyers, operators and investigators, the practical lesson is simple. Use registration data to understand status and sequence, not just the headline expiry date. A domain can be expired, non-transferable and still far from dropping, all at the same time.

Can you still use whois .com to identify the owner

Usually, not from public data alone. That is the short answer.

For many .com domains, public registration records no longer reveal the registrant's personal details. Since GDPR took effect on 25 May 2018, most personal registrant data in WHOIS has been redacted from public view. So if your aim is to identify the owner by name, email address or postal address, a standard public lookup often will not get you there.

That does not mean there are no lawful, practical ways to make contact or gather context. It means you should use the right channels and set expectations properly.

Common alternatives include:

• The registrar's contact or relay channel, if one is provided
• The registrar's published abuse contact, for security or policy issues
• A website contact page linked to the domain
• Public business details shown on the site itself

It is also worth separating two different questions. One is, "Who owns this domain?" The other is, "How can I reach the responsible party?" Public registration data is often poor at answering the first, but still useful for the second because it can point you to the sponsoring registrar and relevant reporting paths.

Since ICANN's RDAP became the definitive source for gTLD registration data on 28 January 2025, current lookup practice has shifted further away from the old expectation that public WHOIS would name the owner directly.

Common mistakes when reading .com registration records

The most common mistakes with whois .com records come from reading too much into too little data. Public registration records can still be very useful, but only if you understand what they do and do not show.

A frequent error is confusing registry data with registrar data. For .com, a registry-level result may be thin. It may identify the sponsoring registrar without giving the richer operational detail users expect. If you stop there, you may miss status information, contact routes or other useful registrar-level data.

Another common mistake is assuming redaction means the domain is unowned or suspicious. In most cases, it means the public display of personal registrant data is limited. That has been normal since GDPR took effect on 25 May 2018.

People also misread expiry dates. An expiry date is not a promise that the domain will delete on that day. Many gTLD names move through post-expiry stages first:

• Auto-renew grace period of up to 45 days
• 30-day redemption period
• 5 days of pending delete

Finally, many older WHOIS tutorials are now simply dated. ICANN's RDAP became the definitive source for gTLD registration data on 28 January 2025, when WHOIS port 43 obligations for gTLD registries and registrars ended. So treat old guides as historical context, not current authority. If you need a quiet second view on a sensitive .com record, Westmore can review it confidentially.