ICANN’s new Registration Data Policy (RDP) is more than a rule change. It is a global effort to modernize how domain registration data is handled, ensuring data collection and disclosure are consistent across all gTLDs, removing the jumble of practices that registrars and registries had to navigate in the past.
At its core, the RDP is about data minimization: collecting only the information that is truly necessary, only when it is required and providing clear rules for how data may be displayed and disclosed. This creates a safer, more predictable environment for everyone who interacts with domain name data from registrants, registrars to end users.
What this means for Hello Registry
We took this opportunity to upgrade our platform in ways that directly benefit the communities we serve. For registrars, this means that every gTLD can now be configured field-by-field and contact-by-contact. The system enforces whether a data element is mandatory, optional or not collected, ensuring that registrars know exactly what is required for each TLD they work with, so they can spend less time wrestling with compliance.
On the other hand, registry operators benefit from confidence and flexibility. We’ve updated all the technical layers—Registration Data Access Protocol (RDAP) and Registration Data Directory Services (RDDS) outputs, escrow formats, audit and reporting tools and policy-driven workflows—so that the rules ICANN has set for publication and disclosure are automatically applied. With these changes, operators can feel at ease knowing that their TLDs remain compliant without having to redesign their systems from scratch.
Real-world scenarios
RDP compliance isn’t one-size-fits-all. Different registry models highlight the benefits of this flexibility.
Moving to a thin registry
When a gTLD operator shifts from a thick model where the registry collects full contact data, to a thin model where no contact information is captured at the registry, operators benefit from reduced compliance risk and lower data-handling overhead. There is no personally identifiable information stored at the registry, simplifying operations and reducing liability, all while making outputs cleaner since privacy services already mask most contact details at the registrar level.
Operating as a thick registry
By contrast, some operators choose a thick registry model, where registrant contact information is maintained at the registry. This approach offers advantages such as more direct oversight of registrant data, faster dispute resolution, stronger abuse-prevention tools and consistent policy enforcement.
In both cases, thin or thick, the Hello Registry platform makes it possible to implement the model that best aligns with the operator’s strategy, while remaining fully compliant with RDP.
Built for every gTLD model
As an Emergency Back-end Registry Operator, Hello has gone beyond basic compliance and ensured that any gTLD, regardless of its operating model, can be run securely and reliably if called upon. Our systems are built to accommodate every possible model—from fully thin minimal data TLDs to thick registries with extensive contact data—and to transition between them seamlessly. For operators, this ensures business continuity today and future-proofing if strategic or regulatory needs evolve tomorrow.
The RDP represents a major shift towards consistency, accountability and trust in how domain data is managed, offering clearer rules and stronger safeguards to registrars, registrants and end users. For registry operators, it gives confidence that compliance does not come at the expense of flexibility. And for Hello Registry, it is another opportunity to deliver what we do best: making complex policy requirements simple, reliable and adaptable for every TLD we operate.
Ready to evolve?
Whether you’re looking to migrate a TLD or simply explore your options, Hello is here to help. We’ll walk you through the models, the trade-offs and the path to compliance, without unnecessary complexity.