ICANN finalized changes to the Registration Data Policy, which sets data processing requirements for gTLDs. Domain registrars and registries are required to comply with the updated Policy by August 2025.
Many of the new Registration Data Policy requirements are already in place at Enom and other registrars: We redact registration data from the public Whois by default and provide a method for third parties to contact the domain owner.
Over the coming months, Enom will implement additional changes to ensure we’re fully compliant. In this post, we cover all changes relevant to Enom reseller partners. For a quick summary, please see our list of action items and key dates.
We’ll collect a reduced minimum data set
In 2018, we reduced the minimum registrant data set we collect and hold to comply with the General Data Protection Regulation (GDPR). ICANN’s updated RDP lets us collect an even smaller list of data. We’ll stop collecting the administrative, billing, and technical contact sets unless specifically required by the registry.
Here’s a comparison of what we currently collect and the reduced set we plan to collect starting June 30, 2025:
| Current minimum data set | New minimum data set |
| Domain Name | Domain Name |
| Registrant Name | Registrant Name |
| Registrant Organization | Will become optional |
| Registrant Street | Registrant Street |
| Registrant City | Registrant City |
| Registrant State/Province | Will be offered to collect (only required to be collected if applicable for the country or territory, as defined in UPU postal addressing standards or other equivalent standards for the country or territory). |
| Registrant Postal Code | Will be offered to collect (only required to be collected if applicable for the country or territory, as defined in UPU postal addressing standards or other equivalent standards for the country or territory). |
| Registrant Country | Registrant Country |
| Registrant Phone | Registrant Phone |
| Registrant Phone Ext | Registrant Phone Ext |
| Registrant Fax | Will no longer be collected |
| Registrant Email | Registrant Email |
| Administrative, Billing, and Technical Contacts | Will no longer be collected |
It’s important to note that this is the minimum data set we’ll collect by default. In some cases, our contract with the registry will require us to collect additional data. For example, .law domains require a number of data fields demonstrating the registrant is an accredited lawyer.
What this means for resellers
Although we recommend that resellers collect the minimum data set, we will not reject orders if a reseller collects and provides us with additional data beyond this minimum data set. However, we will not retain or store any additional data beyond the minimum data set and specific additional data required by the registry for that TLD.
If you send admin, billing, or technical contact info in an API request, our response will not include this data—we’ll return empty contact fields. If your system expects these values to be returned for these fields, you may need to update your API integration.
To assist you:
- We’ve created an ICANN Registration Data Requirements page where you can view which data will be required and which will be optional for each gTLD.
- We’ve updated our testing environment. You can now test your API integration with the new requirements by sending orders for the following TLDs:
- org, which uses the new minimum data set
- .asia, which uses an expanded dataset
You can also use the GetTldDetails command to confirm whether the data set for a specific TLD has been updated; if it has been:
- you’ll see <RDPEnabled>True</RDPEnabled><RDPRule>
- The command will return the updated dataset
Registrants will no longer be able to share “optional’ data with the registry
In 2018, as part of our GDPR implementation, we introduced a “consent management process,” whereby registrants could opt to have us share additional data with the registry, beyond the minimum that our contract with the registry required. We’re doing away with this process. However, we will continue to offer a process for registrants to consent to publish contact information data in the public Whois.
We will delete administrative, tech, and billing contact data
Soon after August 21, 2025, we will delete administrative, technical, and billing contact data, as well as the registrant fax number, from our systems unless the registry specifically requires that data. In rare cases where the registrant contact info is incomplete, we’ll copy the admin contact info to the registrant contact fields before deleting the administrative data.
What this means for resellers
Once this data is deleted, you will no longer have access to it through Enom. If this is data you rely on, you’ll want to securely save it elsewhere.
Requirement for domains where the registrant is an “Organization”
Starting May 28, we will begin contacting registrants who have a value in the Organization field, asking that they review this data and update it if it is no longer correct. If Organization information is provided, the Organization would be considered the domain owner instead of the person listed in the registrant’s first and last name fields. Registrants may also choose to leave the Organization field blank.
While we always redact registration data by default until the domain owner consents to publish it, there may be some instances in which registries choose to display the Organization data in the public Whois.
What this means for resellers
We typically don’t reach out to registrants directly, but we’re now required to do so based on the updated RDP. This gives registrants a chance to review and correct their data, helping to prevent future disruptions for both resellers and registrants.
You also may wish to update your domain registration and management flow for your customers; if you provide them the opportunity to add an org field value when they register or update their domain, please ensure they understand that:
- They should leave the organization field blank, unless they want the organization to be the legal registrant
- Data included in the organization field may be published in the public Whois by the registry
Action items for resellers and key dates
May 28, 2025 – Outreach to Registrants
What’s happening:
Enom will start sending a one-time email to registrants with data in the Organization field of their contact records. The email will explain that:
- If there’s any information in the Organization field, that organization will be considered the legal owner of the domain.
- If a registrant wants to be listed as the domain owner as an individual, the organization field must be left blank
What resellers need to do:
Before May 28, 2025, we recommend that you prepare your support teams to answer questions related to enabling Whois Publicity.
June 20, 2025 – We’ll no longer collect, store, or return admin, billing, and technical contact data
What’s happening:
Enom will no longer store admin, billing, or technical contact data for gTLDs, unless it’s specifically required by the registry. From this point forward, our API will still accept requests containing additional data, but we’ll only return the new minimum data set for each gTLD, except in rare cases where the registry requires additional data. If you send a request containing billing, admin, or technical contact data, our response will include empty fields for these contacts.
What resellers need to do:
If you want to continue collecting admin, billing, and technical contact data and retaining access to it, you’ll need to implement your own method for collecting and storing it going forward.
You can now use our new ICANN Registration Data Requirements page to view the required and optional data for each gTLD.
For API users: if your system expects all original data to be returned, you may need to adjust your integration.
We’ve updated our testing environment; you can now test your API integration with the new requirements by sending orders for the following TLDs:
- org, which uses the new minimum data set (see details above)
- .asia, which uses an expanded data set (see details above)
August 21, 2025 – The updated RDP officially takes effect
What’s happening:
If there is any information in the Organization field of a registrant’s domain contact details, the Organization officially becomes the domain owner.
What resellers need to do:
You may wish to update your domain registration and management flow for your customers; if you provide them the opportunity to add an org field value when they register or update their domain, please ensure they understand that:
- Data included in the organization field may be published in the public Whois by the registry
- They should leave the organization field blank, unless they want the organization to be the legal registrant
As stated above, you also may want to:
- Find a means to independently collect and store admin, billing, and technical contact data, if you wish to continue keeping this data
- Update your API implementation, if applicable.
Next steps
As more information becomes available, we’ll reach out to you well in advance. We’ll notify the email associated with your reseller account, and we’ll also include updates in our general newsletter—click here to sign up.