Do providers have a process for registry verification requests on existing domains?

[NiceNIC]

A registry verification request can become complicated when the domain has already been active for years.

The .AT update brings up an interesting operational question for providers.

Do you have a process for handling registry compliance requests from customers?

Source:
https://www.nic.at/en/how-at-works/faqs/nis2-nisg2026-en

 

[FireVM.]

Most registrars have a process for registry/registrant verification requests involving existing domains, although the exact procedure depends on the TLD and registrar. Registry verification and registrar verification aren't always the same thing. A registry can have its own verification requirements for a particular TLD, while the registrar may have additional procedures for verifying the customer's registration data.

 

[NiceNIC]

Most registrars have a process for registry/registrant verification requests involving existing domains, although the exact procedure depends on the TLD and registrar. Registry verification and registrar verification aren't always the same thing. A registry can have its own verification requirements for a particular TLD, while the registrar may have additional procedures for verifying the customer's registration data.

That's right. With .AT, not every existing domain needs verification. But once a request is issued, there's only 21 days to get it sorted before the domain can go on serverHold. That could be a headache for resellers managing older client domains.