--- id: "data-accuracy" kind: "glossary-term" title: "registration data accuracy" language: "en" category: "Registration data and privacy" updated: "2026-10-10T10:28:55Z" canonical: "https://tldlog.com/glossary/data-accuracy/" translations: es: "https://tldlog.com/es/glosario/exactitud-datos-registro/" de: "https://tldlog.com/de/glossar/richtigkeit-registrierungsdaten/" fr: "https://tldlog.com/fr/glossaire/exactitude-donnees-enregistrement/" it: "https://tldlog.com/it/glossario/esattezza-dati-registrazione/" pt-BR: "https://tldlog.com/pt/glossario/exatidao-dados-registro/" ru: "https://tldlog.com/ru/glossariy/tochnost-registratsionnykh-dannykh/" zh-Hans: "https://tldlog.com/zh/cihui/zhuce-shuju-zhunquexing/" --- # registration data accuracy How correct and usable the contact details in a domain record are. Registrants must give true data and keep it up to date, and gTLD registrars must check parts of it. Wrong data can lead to suspension or cancellation. How to measure accuracy now that most data is hidden is still debated. Registration data accuracy is whether the contact details behind a domain name are true, complete and working. The holder must give correct details and keep them current, and the registrar must check some of them. Wrong details can cost the holder the domain. ## What registration data accuracy means For generic top-level domains (gTLDs), the duty comes from ICANN's Registrar Accreditation Agreement (RAA). The registrant must give "accurate and reliable contact details". As of October 2026, they must correct them within seven days of any change. There is no single definition beyond these rules. In the ICANN community, some argue that being able to reach the registrant is enough, while others want identity checks too. ## Why accuracy matters Correct details let the registrar and others reach the holder about technical problems, transfers, disputes and abuse. The European Union's NIS2 directive links accuracy to the security and stability of the DNS. Since the GDPR, most personal data is hidden from public lookups. ICANN says the duties did not change, but errors became harder for outsiders to spot. Hidden data is not the same as wrong data. ## Verification checks and reminders As of October 2026, the RAA's RDDS Accuracy Program Specification (formerly the WHOIS Accuracy Program Specification) sets two checks for gTLD registrars: - Validation: the email address, phone number and postal address are correctly formatted, the postal address for its country. - Verification: the registrant confirms the email address or the phone number, for example by returning a unique code. Both happen within 15 days of a new registration, an incoming transfer or a change of registrant, and within 15 calendar days of any change to the contact details. Identical data already verified need not be checked again unless there is reason to doubt it. A bounced email forces a new verification. The Registration Data Reminder Policy (RDRP) adds a yearly prompt. Before each anniversary of the creation date, the registrar shows the registrant the current data and warns that false contact information can lead to cancellation. If everything is correct, no action is needed. The updated policy, formerly the WHOIS Data Reminder Policy, had to be implemented by 21 August 2025. Registrars must also investigate inaccuracies reported by anyone and take reasonable steps to correct them. ## What happens if your data is wrong If the registrant of example.com ignores the verification email, on day 16 the registrar must verify the data by hand or suspend the domain until it is verified. Wilfully false data, a wilful failure to update, or no reply for more than 15 days to the registrar's questions about accuracy is a material breach of the registration agreement. The registrar must then terminate or suspend the name, or place it on clientHold and clientTransferProhibited until the data is validated. The website and email can stop working. Anyone can report suspected wrong data to ICANN Contractual Compliance, with evidence such as a bounced email. Valid complaints go to the registrar, which must investigate. Most investigated cases ended with the name suspended or cancelled: 79% from January 2017 to May 2018, and 69% from June 2018 to December 2020. ## Measuring accuracy and the policy debate ICANN's WHOIS Accuracy Reporting System (ARS) tested records drawn from samples of 10,000 to 12,000 and reported every six months from December 2015 to June 2018. It measured whether data was well formed and whether it worked, never whether the person was who they claimed to be. In the last cycle, 56% of domains passed all operability tests, though 98% of records had at least one working email address or phone number. ICANN paused it after the GDPR, and as of October 2026 it has not restarted. The GNSO Council set up the Registration Data Accuracy Scoping Team in July 2021. In September 2022 the team proposed a registrar survey and a registrar audit. The work was paused in November 2022, and in September 2024 the Council deferred the two proposals for six more months. In 2025 the Council approved four recommendations from a small Council team: re-examine validation and verification, create education materials for registrants, mark names suspended for wrong data in their records, and discontinue the Scoping Team's work. The first cites the INFERMAL study, which reported 70% fewer malicious registrations where contact details were checked before or during registration. The small team did not endorse the study's methods or conclusions. ## EU rules: NIS2 and ccTLDs ccTLDs are not bound by the RAA. In the European Union, Article 28 of NIS2 requires TLD registries and registrars to keep accurate and complete data, including the registrant's name, email and phone, and to publish their verification procedures; a recital adds that at least one means of contact should be verified. Member states had to apply it through national law from 18 October 2024, so details differ by country. For .eu, EURid published a Registration Data Verification Policy in October 2024 under Belgium's NIS2 law. A name flagged as possibly linked to abuse is suspended at once and reactivated only after its data is verified; if not verified within a set time, it is withdrawn and released for registration. For .es, Spain's national plan for .es names makes the applicant responsible for the truth and accuracy of their data and requires immediate updates. Red.es does not verify data at registration; it checks afterwards, including on reports from public bodies. As of October 2026, the registrar, holder and administrative contact get 15 calendar days to fix the data while the name keeps working. Then Red.es opens a special cancellation procedure: the holder has 30 calendar days to respond, and the name stops working after the first 10. Holders unsure of their position should ask their registrar, Red.es or a lawyer. ## Sources - [Registrar Accreditation Agreement](https://itp.cdn.icann.org/en/files/accredited-registrars/registrar-accreditation-agreement-21jan24-en.htm) - [ICANN Organization Enforcement of Registration Data Accuracy Obligations Before and After GDPR](https://www.icann.org/resources/pages/registration-data-accuracy-obligations-gdpr-2021-06-14-en) - [GNSO Council Accuracy Small Team Summary](https://gnso.icann.org/sites/default/files/policy/2025/draft/gnso-council-accuracy-small-team-summary-31jul25-en.pdf) - [EURid: Data quality](https://eurid.eu/en/about-eurid/data-quality/) - [Dominios.es: Cancela un dominio](https://www.dominios.es/gestiona-tu-dominio/cancela-un-dominio) ## related terms - [WHOIS Accuracy Program Specification](https://tldlog.com/glossary/whois-accuracy-program-specification/) - [contact verification](https://tldlog.com/glossary/contact-verification/) - [RDRP](https://tldlog.com/glossary/rdrp/) - [WHOIS ARS](https://tldlog.com/glossary/whois-ars/) - [Registration Data Accuracy Scoping Team](https://tldlog.com/glossary/accuracy-scoping-team/)