Registrant verification announcement

New regulations and procedures as per ICANN’s 2013 Registrar Accreditation Agreement are now live. Here’s some important information you need to know:

Validating a registrant’s email address

  •  Effective immediately, the registrant contact needs to be validated upon the purchase or transfer of a domain name, or if the registrant’s first name, last name or email address have been modified. OpenSRS sends an email that, like our other features, has white label/branding capabilities.
  • Reminder emails will be re-sent on days 5, 10 and 13 within the 15-day validation window; messages on days 10 and 13 of this process are sent to the Admin, Tech and Billing contacts as well. These reminders can be disabled.
  • The same process takes place if a WHOIS Data Reminder Policy (WDRP) notice, 30 day expiration notice or 5 day expiration notice bounce. It’s therefore crucial to ensure the WHOIS data your customer provides is correct.
  • Failing to receive a response within 15 days requires us to suspend the name. As a result, the name will be placed on ClientHold, rendering the domain name inactive.
  • This process applies to all gTLDs. There is no impact to existing names as long as they are not modified, and WDRP/expiration notices do not bounce.

As a result of these changes, we have introduced a number of features:

  • White label/branding capabilities for all registrant validation and reminder emails;
  • The ability to resend validation e-mails through the control panel and API (send_registrant_verification_email);
  • Additional information within a new API call regarding a name’s validation status (get_registrant_verification_status);
  • The ability to filter names by validation status in the new control panel;
  • The ability to send optional reminder e-mails 5, 10 and 13 days after the validation process is triggered.

You can also consult our registrant validation FAQ, located in our knowledge base.

Important: Increased data validation

The 2013 RAA requires registrars to ensure email addresses, postal addresses and phone numbers are formatted properly as per specific RFCs and ITU specifications. As a result, please ensure contact data sent is valid (for example, phone numbers formatted properly and postal/zip codes corresponding to the correct country) in order to avoid any ordering issues.

 

23 thoughts on “Registrant verification announcement

  1. The API function “resend_registrant_verification_email” appears not to exist. However, I found “send_registrant_verification_email” in the documentation and that works via the API but I don’t know if it does the same thing. Can you clarify?

    Also, although I found the ability to search for verification status in the new Control Panel, I can’t find a mechanism to resend verification emails via the RWI/Control Panel.

  2. The API function “resend_registrant_verification_email” appears not to exist. However, I found “send_registrant_verification_email” in the documentation and that works via the API but I don’t know if it does the same thing. Can you clarify?

    Also, although I found the ability to search for verification status in the new Control Panel, I can’t find a mechanism to resend verification emails via the RWI/Control Panel.

  3. Hi gnshapiro,

    The command “send_registrant_verification_email” is the correct API call to use and it will send or resend the verification email.

    You can only resend the verification email within the control panel. When managing a domain name, under the Actions menu, you’ll see an option to resend the registrant verification email.

  4. Hi gnshapiro,

    The command “send_registrant_verification_email” is the correct API call to use and it will send or resend the verification email.

    You can only resend the verification email within the control panel. When managing a domain name, under the Actions menu, you’ll see an option to resend the registrant verification email.

  5. Hi. We are receive mails for validation in domains that we don’t modified, from “registrarmail.net” that redirect to “approve.domainadmin.com” . This mails are phising, beware!!!

  6. Hi. We are receive mails for validation in domains that we don’t modified, from “registrarmail.net” that redirect to “approve.domainadmin.com” . This mails are phising, beware!!!

  7. Hi,

    I don’t see that option under the Actions menu..

    The API command get_registrant_verification_status works for me, I was receiving ‘Invalid Command: resend_registrant_verification_email’, (this is what the blog post says).. I suppose your reply above indicates that the actual command is ‘send’ instead of ‘resend’. Perhaps it would be good to update the blog post?
    Thank you,

  8. Hi,

    I don’t see that option under the Actions menu..

    The API command get_registrant_verification_status works for me, I was receiving ‘Invalid Command: resend_registrant_verification_email’, (this is what the blog post says).. I suppose your reply above indicates that the actual command is ‘send’ instead of ‘resend’. Perhaps it would be good to update the blog post?
    Thank you,

  9. This is a ridiculous policy. Clients BARELY keep their payment information up to date, what makes you think that they will keep their email contact address up to date also? I, as a reseller of Opensrs with more than 1,500 domains, was NOT aware of this. No one in my staff knew about it until today. Was an email sent to resellers about this? I don’t even see the announcement in the opensrs portal! I learned of this today when all of a sudden some of my clients had their domains suspended.

    Whoever made the decision on this has no experience with clients in the hosting industry, how difficult it is to go after customers to keep their contact information up to date and has no concept of human behavior and psychology. This change will be affecting the reputation of all resellers.

  10. This is a ridiculous policy. Clients BARELY keep their payment information up to date, what makes you think that they will keep their email contact address up to date also? I, as a reseller of Opensrs with more than 1,500 domains, was NOT aware of this. No one in my staff knew about it until today. Was an email sent to resellers about this? I don’t even see the announcement in the opensrs portal! I learned of this today when all of a sudden some of my clients had their domains suspended.

    Whoever made the decision on this has no experience with clients in the hosting industry, how difficult it is to go after customers to keep their contact information up to date and has no concept of human behavior and psychology. This change will be affecting the reputation of all resellers.

  11. I NEVER got a notification from OpenSRS about this massive change from ICANN. Expect many downed (big and popular to boot) web sites this year because of this dumb policy.

  12. I NEVER got a notification from OpenSRS about this massive change from ICANN. Expect many downed (big and popular to boot) web sites this year because of this dumb policy.

  13. Implementation of this policy is turning out to be a train wreck for resellers.

    We have been asking OpenSRS for some help (and management input) on this one for some weeks now – nothing.

    Tucows have really dropped the ball on this one. Someone in management needs to give this attention urgently.

  14. Implementation of this policy is turning out to be a train wreck for resellers.

    We have been asking OpenSRS for some help (and management input) on this one for some weeks now – nothing.

    Tucows have really dropped the ball on this one. Someone in management needs to give this attention urgently.

  15. This is a well-meaning but disastrous initiative. Websites on domains registered with whois info provided in good faith are going off-line. I can understand the case for suspending Mickey Mouse registrations; but not taking down legitimate websites on the strength of a bounced email. Other registrars are not being so over-zealous as Tucows. Please restore suspended domains asap and review.

  16. I’ve already had a client’s domain shut down because of this and it created a nightmare for our business relationship with them. Although well intended, this is a very stupid policy and it needs to be reconsidered.

  17. I’ve already had a client’s domain shut down because of this and it created a nightmare for our business relationship with them. Although well intended, this is a very stupid policy and it needs to be reconsidered.

Leave a Reply