Domains: ICANN / RAA Domain Contact Verification

Modified on Sun, 8 Dec at 6:47 PM

Answer ID 1633


*Also see the HelpDesk article: RAA Registrant FAQs


I just received an email notice about verifying my contact information. Is this verification email genuine?

 

If the verification email was sent from our company email address, and links to a "name-services.com" address, then it is genuine. The link provided in the email, from name-services.com, is what we use for several services, including domain verification. As per the new ICANN rules, domain contact information must be verified when a new domain name is registered, or when the registrant contact information is updated. 


 

What is the RAA Verification process? 


Note: Info on this page was taken from an Enom help article, linked here: https://help.enom.com/hc/en-us/articles/115003362687-Verifying-registrant-contact-information#top


The Registrar Accreditation Agreement (RAA) requires us to contact registrants regarding the contact information on their domains. Registrants are required to verify their contact details when registrant contact information is updated. We send yearly emails to ensure contact details are accurate and up-to-date. Domains can be suspended for non-compliance if they are not verified. Suspension causes the website and email service associated with the domain to stop working. The suspension will not affect a domain's lifecycle, and it will still be possible to renew the domain if suspended. Scroll down on this page to read the sections laid out below, or click the links below to go straight to a section on the Enom help article page:



Click here to go to the bottom of this page about "registrar lock after contact change", and additional notes. 


Triggering the verification process

The RAA verification process is triggered when a domain is newly registered or whenever changes to the registrant contact's first name, last name, or email address. This process does not apply to changes to administrative, technical, or billing contacts. If multiple domains were registered with the same contact information, only one email would go out to verify all domains. Registrants must verify newly registered domains within 14 days, and existing domains within seven days. The domain will be suspended if the registrant does not verify the contact information within this timeframe.


Important: Make sure to add donotreply@name-services.com to your email allow-list. 


For info about whitelisting these email addresses at your email provider, see the HelpDesk article: Account: Whitelist our sending email addresses to help with delivery of domain account emails




Back to top


Resending verification emails

If you manage your domain through the Enom access domain management portal, you can trigger a verification email by submitting another contact update. Only the most recent update will be in effect, and all prior changes will be cancelled.


Resending from an account

  1. Sign in to your account.
  2. Select Pending suspensions from the account overview.
    Note: This is an account report that defaults to displaying information from the previous thirty days. If you do not see your domains, try selecting an earlier start date and clicking Run report.
  3. Click on Resend.
  4. The registrant email address of the domain will be sent an email with the subject:
    "IMMEDIATE VERIFICATION required for [your domain]." 
    Note: The email will be sent from donotreply@name-services.com, googleclients@enom.com, or info2@enom.com. It can take up to half an hour for the email to arrive. For info about whitelisting these email addresses at your email provider, see the HelpDesk article: Account: Whitelist our sending email addresses to help with delivery of domain account emails


5. The email will contain a link that you must click to complete the verification.

Important: The link in the email will contain the domain raa.name-services.com. It is possible to spoof the "From" field of an email, so do not click on any link that is not from this domain. The complete link should resemble this:


http://raa.name-services.com/raaverification/verification.aspx?VerificationCode=[a random string]

6. After clicking the link, you should see a confirmation screen after verifying through the link.



7. The new and old registrants will also be sent two emails summarizing the changes.

  • DOMAIN CONTACT UPDATE CONFIRMATION EMAIL (NEW REGISTRANT)
  • DOMAIN CONTACT UPDATE CONFIRMATION EMAIL (OLD REGISTRANT)



Resending from the suspended webpage

If the verification times out, the domain will be suspended. The domain's DNS will be changed to display an ICANN verification website.

1. Go to your domain in a web browser.

2. You will see a suspended page with a verification field. Enter the numbers into the empty field and click Resend verification email.



3. The registrant email address of the domain will be sent an email with the subject:
"IMMEDIATE VERIFICATION required for [your domain]." 
Note: The email will be sent from donotreply@name-services.com, googleclients@enom.com, or info2@enom.com. Depending on the verification queue, it can take up to half an hour for the email to arrive.


4. The email will contain a link that you must click to complete the verification.

 

Important: The link in the email will contain the domain raa.name-services.com. It is possible to spoof the "From" field of an email, so do not click on any link that is not from this domain. The complete link should resemble this:

http://raa.name-services.com/raaverification/verification.aspx?VerificationCode=[a random string]

5. After clicking the link, you should see a confirmation screen after verifying through the link.


 

6. The new and old registrants will also be sent two emails summarizing the changes.

  • DOMAIN CONTACT UPDATE CONFIRMATION EMAIL (NEW REGISTRANT)
  • DOMAIN CONTACT UPDATE CONFIRMATION EMAIL (OLD REGISTRANT)

Back to top



Dealing with a suspended domain

There are different methods to unsuspend a domain.


Once the suspension is dealt with, another page will replace the suspended one.
Note: It takes time to point back to the previous host records and bring the website or email back online due to DNS propagation.


 

If you click a verification link and see an invalid page, you should check the domain to see if the new contact details are present. If not, resend the verification email.



Back to top



 

 

*Registrant contact information verification changes (December 2016) - see article "Change registrant info - 60 day lock - (effective December 2016)"

  • This policy comes into effect any time a gTLD domain registrant’s first name, last name, or email address is changed
  • Whenever a change is made, both the current registrant and the new registrant must confirm the change (even if those two are actually the same person or entity)
  • Both registrants will receive notification that the change is pending, and be given the ability to decline the change
  • After the change has been confirmed, the domain cannot be transferred to a new registrar for 60 days. However you can disable this 60 day lock in your account default settings. Please see the article: "Enable / Disable 60 day transfer lock for contact information changes"


Note: Full information from ICANN about the RAA verification process can be found here: https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en


Note: See the full ICANN transfer policy here: https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en


Note: When changing the contact information for multiple domains at one time, a verification email is sent for each. So, if you updated 10 domains, you would receive 10 contact verification emails. However, if identical contact information is supplied for the domains, verifying a single domain will verify all domains with the same contact details.

Note: Automatic RAA verificaton emails are sent out from info2@enom.com. Manually sent verification emails are sent from customercare@enom.com


Back to top

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article