Hi Roger, Thank you for your message. We are currently checking internally regarding your question on Registrar access to Registry URS Contacts in NSp. We’ll get back to you as soon as we have more clarity. Best, Antonietta From: rcarney--- via RPM-IRT <rpm-irt@icann.org> Reply-To: "rcarney@godaddy.com" <rcarney@godaddy.com> Date: Tuesday, October 7, 2025 at 12:50 PM To: "rpm-irt@icann.org" <rpm-irt@icann.org> Subject: [RPM-IRT] Re: Update on Implementation of URS Recommendation #12 (Group 3) Good Afternoon, Thanks Antonietta for the continued updates as we make progress. I will admit that I do not access NSp unless I am told to, so I wanted to get clarity on Registrar access to Registry URS Contacts. Specifically, do/should Registrars have access to Registry URS Contacts in NSp? I don't think this is technically required by Rec 12/URS Procedures paragraph 4, but it is the only link that this not mentioned below between the three parties (Provider/Registry/Registrar). Thanks Roger ________________________________ From: Antonietta Mangiacotti via RPM-IRT <rpm-irt@icann.org> Sent: Tuesday, October 7, 2025 1:25 PM To: rpm-irt@icann.org <rpm-irt@icann.org> Cc: Eduardo Duarte <eduardo.duarte@icann.org> Subject: [RPM-IRT] Update on Implementation of URS Recommendation #12 (Group 3) Dear RPM IRT, We are writing to provide an update on the work related to the implementation of Group 3 recommendations. This group includes one recommendation, URS Final Recommendation #12: “The Working Group recommends that the ICANN org, Registries, ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Dear RPM IRT, We are writing to provide an update on the work related to the implementation of Group 3 recommendations. This group includes one recommendation, URS Final Recommendation<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...> #12: “The Working Group recommends that the ICANN org, Registries, Registrars, and URS Providers take appropriate steps to ensure that each other’s contact details are up to date in order to effectively fulfill the notice requirements set forth in the URS Procedure paragraph 4.” Below is a summary of the work that was undertaken to ensure all relevant parties have access to accurate and current contact information in order to ensure the efficacy of the URS process. 1. URS Providers → Registrars (New Process) On 30 September 2025, ICANN org launched a new process to allow URS Providers to download, on a daily basis, the Registrar URS Primary and Secondary contact information by downloading a Comma-Separated Values (CSV) file containing the relevant details. The new file will be updated every six hours with the latest contact information available to ensure that URS Providers have up-to-date information. This process is facilitated through the Naming Services portal<https://urldefense.com/v3/__https:/www.icann.org/en/contracted-parties/accre...> (NSp), where new URS contact roles—specifically, URS Primary and Secondary Contacts—were introduced. These fields were pre-populated using the registrar’s Uniform Domain Name Dispute Resolution (UDRP) Primary and Secondary contact data. ICANN org communicated the creation of these new roles to the Registrars on 27 May 2025<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/contracted-par...>. Registrars were also reminded that per the URS High-Level Technical Requirements<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/te...>, Accredited Registrars are required to maintain the URS contact information up to date for the purpose of receiving URS communications. Registrars who wish to review or make any changes to their URS Primary or Secondary contact information in the NSp, can submit a Contact Update Request in the portal. In addition, please note that the URS High-Level Technical Requirements<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/te...> already included the steps for this process (see page 7). Since the process has now been created, there is no need to update the existing requirements. 1. Registries → Registrars (New Process) Registry Operators will also be able to access the Registrar URS Primary and Secondary contact information saved in NSp. The communication sent to registrars regarding the Registrar URS Contact Information—now available to URS Providers and gTLD Registry Operators—will be posted here<https://urldefense.com/v3/__https:/www.icann.org/en/contracted-parties/commu...>. 2. URS Providers → Registries (Existing Process) URS Registry Operator contact information is already available in NSp, and URS Providers currently have the ability to download these details. In addition, the functionality mentioned above to submit contact update requests for URS roles already exists for Registry Operators; therefore, a new process for URS Providers to obtain up to date URS Registry Operator contact information is not being developed. However, the URS High-Level Technical Requirements<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/te...> will need to further be revised to reflect the existing process, and will be shared with the IRT for review. In addition, please note that the process for URS Providers to access Registrars’ URS contact information (see item #1) was modeled after this existing process used for URS Registry Operator contacts. Please note that ICANN communicates with contracted parties and URS Providers regarding URS-related matters through established channels, including direct correspondence via account managers. Additionally, both ICANN and contracted parties can access the URS Providers' contact information through the URS page on the ICANN website, which provides links to the various URS Provider websites: https://www.icann.org/urs-en<https://urldefense.com/v3/__https:/www.icann.org/urs-en__;!!Hj18uoVe_Lnx!s7qQzDWtBGgCegTc1_POER8LZCc_iCy6KH6peX8IBL3_nz1ZiUaB7l5l_D442KCuxHqdOzcIflEdmI4$>. Please let us know if you have any questions related to the information above. Thank you! Best, Antonietta