The Admin-C (ad­min­is­tra­tive contact) was his­tor­i­cal­ly re­spon­si­ble for the ad­min­is­tra­tive man­age­ment of a domain, including approving changes to domain records, name servers, or contact details. This person also served as a central point of contact for reg­is­trars and in dispute cases. In 2018, global WHOIS policies were revised following new data privacy re­quire­ments, par­tic­u­lar­ly the EU’s GDPR, and as a result the separate Admin-C role is no longer publicly listed for most modern domain reg­is­tra­tions and is often handled in­ter­nal­ly by the registrar.

Domain Name Reg­is­tra­tion
Build your brand on a great domain
  • Free Wildcard SSL for safer data transfers 
  • Free Domain Connect for easy DNS setup

What is Admin-C?

The Admin-C (Ad­min­is­tra­tive Contact) was his­tor­i­cal­ly the official contact person for the ad­min­is­tra­tive man­age­ment of a domain, such as updating contact details or name servers. This in­di­vid­ual was not always the domain owner, although that was often the case for private reg­is­tra­tions.

Today, a separate Admin-C role is no longer required for most modern domain reg­is­tra­tions. Following global WHOIS policy changes in 2018, par­tic­u­lar­ly after new data privacy reg­u­la­tions such as the EU’s GDPR, many reg­is­trars sim­pli­fied the tra­di­tion­al contact structure. As a result, ad­min­is­tra­tive re­spon­si­bil­i­ties are typically handled by the reg­is­trant, the registrar, or through stan­dard­ized support channels.

In the past, the Admin-C also served as the primary point of contact for registrar inquiries or domain disputes. Today, these matters are usually managed through official registrar contact addresses or registry-operated pro­ce­dures. While some top-level domains (TLDs) or country-code domains may still tech­ni­cal­ly support an Admin-C field, this in­for­ma­tion is generally not publicly visible due to current ICANN Reg­is­tra­tion Data Policy re­quire­ments and privacy standards.

Note

Under the current ICANN Reg­is­tra­tion Data Policy, most generic TLDs such as .com and .net no longer require a publicly listed Admin-C. Some reg­istries may still support the role in­ter­nal­ly or as an optional contact field, but pub­li­ca­tion of personal contact data is now sig­nif­i­cant­ly re­strict­ed.

Evolution of the Admin-C role

Before the in­tro­duc­tion of the GDPR on May 25, 2018, the Admin-C was a central element of domain reg­is­tra­tion data. The role referred to a natural person listed in the WHOIS database as the ad­min­is­tra­tive contact and publicly reachable for questions regarding the domain. The recorded in­for­ma­tion — including name, address, email address, and phone number — was openly ac­ces­si­ble and could be viewed by au­thor­i­ties, companies, or anyone per­form­ing a domain lookup.

After new privacy re­quire­ments came into force, the handling of reg­is­tra­tion data changed worldwide. To comply with in­ter­na­tion­al data pro­tec­tion standards, ICANN and reg­is­trars re­strict­ed the pub­li­ca­tion of personal WHOIS data. As a result, the Admin-C is no longer publicly displayed for most top-level domains. Instead, reg­is­trars now typically provide stan­dard­ized contact methods such as web forms or func­tion­al email addresses for general inquiries and for reporting illegal or abusive domain use (domain abuse).

Note

The changes did not only affect the Admin-C. Ad­di­tion­al contact roles pre­vi­ous­ly listed in WHOIS — such as the technical contact (Tech-C) and zone ad­min­is­tra­tor (Zone-C) — are also generally no longer publicly published. Modern reg­is­tra­tion systems rely on registrar-managed contact channels rather than exposing personal contact data.

How to find out Admin-C

Even though the classic Admin-C role no longer exists, you can still obtain contact options for a domain. To do so, you can perform an RDAP query. RDAP is the modern successor to the WHOIS lookup and provides struc­tured reg­is­tra­tion in­for­ma­tion such as the registrar, reg­is­tra­tion dates, and status codes. Personal contact data, however, is usually redacted for privacy reasons.

Instead of dis­play­ing a person’s name or address, RDAP records typically provide a registrar-managed contact method, for example a web form or anonymized email address that forwards messages to the domain holder.

In certain sit­u­a­tions, au­tho­rized parties — such as law en­force­ment agencies, trademark owners, or attorneys involved in a legal claim — may request dis­clo­sure of contact data from the registrar. Access is granted only after ver­i­fi­ca­tion and a doc­u­ment­ed le­git­i­mate interest; ordinary users generally cannot obtain personal contact details.

Domain ownership and personal data col­lec­tion

Unlike the former Admin-C role, reg­is­trant data is still collected during domain reg­is­tra­tion. The reg­is­trant is the con­trac­tu­al holder of the domain reg­is­tra­tion with the registrar. While domains are often referred to as being “owned,” they are legally reg­is­tra­tion rights granted under a contract rather than property in the tra­di­tion­al sense.

The reg­is­trant can be either a natural person or a legal entity, such as a company including its legal form suffix (e.g., LLC, Inc., Ltd.). During reg­is­tra­tion, the following in­for­ma­tion is typically required:

  • name of the reg­is­trant
  • mailing address
  • telephone number
  • email address

Although this data is collected by the registrar, most personal details are no longer publicly displayed in RDAP or WHOIS results due to current ICANN Reg­is­tra­tion Data Policy and privacy reg­u­la­tions. Public lookups generally show non-personal data such as the registrar, reg­is­tra­tion and ex­pi­ra­tion dates, domain status, and name servers.

Technical data — including name server in­for­ma­tion and, where ap­plic­a­ble, DNSSEC keys — remains necessary to ensure that the domain functions properly and continues to be part of the publicly available reg­is­tra­tion record.

Domain Checker

Reviewers

Go to Main Menu