The Registrant Verification (RV) process is a 15-day window during which a registrant must provide an affirmative response to an email that OpenSRS sends to them. The verification process applies to all generic TLDs.
Registrant Verification overview
The domain owner must confirm their contact details via an email sent by OpenSRS. Failure to confirm the elements results in the domain becoming suspended and services being disabled. The verification process applies to all gTLDs. Registrant verification does not affect domain renewals.
The registrant
The registrant in OpenSRS is the organization contact record found in the Reseller Web Interface (RWI) or the owner contact record in the Reseller Control Panel (RCP).
Note: Only the owner contact is subject to verification, not the administrator, billing, or technical contact.
Verification process
The verification process is a 15-day window during which a registrant must provide an affirmative response via an email sent to them.
The email displays a link the registrant must click to take them to the verification page. The verification page shows the email address and first and last name used to register the domain. The page also includes a link to the domain registration terms and conditions and a checkbox the registrant must click to confirm that they agree to the terms and conditions.
Failure to respond to this email results in domain suspension. Services on the domain cease working while under suspension.
Data sets
OpenSRS verifies three pieces of registrant contact data: first name, last name, and email address.
When a registrant purchases, transfers, or updates a domain's registrant contact information, OpenSRS first checks to see if a previously verified record exists for that combination of first name, last name, and email address.
The domain is automatically verified when an exact match exists, and no further action is required. When an exact match does not exist, the registrant receives an email asking them to confirm their data. For example, John Doe john@example.com differs from Johnathan Doe john@example.com, requiring independent verification.
Verification status
Locate the registrant verification status in the RCP on the domain list or when viewing the domain details. A list of all domains and their RV status is available as a report to download manually or automatically send daily.
To find the status in the RCP:
- Login to the RCP.
- Enter the domain name in the quick search field and click Search.
- The registrant verification status is in the domains overview section.
Statuses
| Unverified | The verification process is not in progress. The domain does not need to be verified. |
| Pending | The verification process is initiated. |
| Verifying | The verification process is in progress and is waiting for the registrant's response to the email. |
| Verified | The registrant is verified. |
|
Suspended |
OpenSRS interrupts the DNS and prevents the domain from resolving. The domain is set to ClientHold status. |
| Manual review | The registrant data has been submitted and undergoing manual verification by the Tucows compliance team. |
Reports
The CSV file available is a spreadsheet including the current email address for the domain name, the date the verification began, the suspension date, and the registrant's first and last names.
To obtain a report:
- Login to the RCP.
- Click on Download daily registrant verification CSV file.
Verification triggers
Any new registration, transfer in, contact updates, WDRP bounce, or mandatory renewal reminders bounce triggers the verification process.
Changing any registrant contact details initiates the verification process for unverified domains. Changing the registrant's first name, last name, or email address on verified domains triggers the verification.
When WDRP messages bounce, the domain enters the verification process.
Owner changes
Completing the ICANN trade process completes the registrant verification process. Registrants must verify the new contact info as part of the process. Only the new address receives the registrant verification request.
Messaging
The registrant receives an email to verify their contact information on days one, five, ten and 13. On day 16, when a registrant hasn't verified their data, they receive an email informing them that we have set the domain to suspended status.
Note: Messages take up to 24 hours to go out.
On days 10 and 13, the admin and billing contacts for the domain receive emails notifying them of the upcoming suspension. These admin/tech notification messages do not include the link to verify the domain details.
Timing
All verification emails are sent out immediately except for suspensions, and the five, 10, and 13-day reminders go at 04:00 UTC. When manually sending the email, it goes out within minutes.
Resending messages
When verification is required, the message may be resent. The option to resend the verification email is available for sub-resellers in the RWI.
Resend via RCP
- Login to the RCP.
- Enter the domain name in the quick search field and click Search.
- Click Resend verification email from the domains overview section.
Resend via RWI
- Login to the RWI.
- Enter the domain name in the view domain field under the domain registration administration section and click Query.
- Click Resend registrant verification email from the domain management section.
- Click Ok.
Toggle registrant verification messaging.
Resellers choose whether their daily notice is enabled or not through the RCP or the RWI.
Toggle reseller messaging via RCP
- Log into the RCP.
- Click Messaging and confirmation.
- Toggle the switch for the registrant verification status report.
Toggle reseller messaging via RWI
- Login to the RWI.
- Click View message templates.
- Toggle the checkmark from the box beside Registrant verification message to RSP under the registrant validation messaging section.
- Click Submit at the bottom of the page.
Customization
Logos uploaded to the branding page are displayed instead of the OpenSRS logo. Resellers can change the link registrants see in the RV message, and add custom header and footer texts. It is possible to specify a custom domain as well.
The text of the message body cannot be modified, but resellers can add text above and below the existing text using snippets.
Modify the verification hostname and URL through the RCP and RWI.
Note: When setting up a custom hostname, configure the CNAME record on the address pointing to approve.domainadmin.com and allow it to propagate fully.
Customization via RCP
- Login to the RCP.
- Select Account settings.
- Click the Branding tab.
- Click Edit in the registrant verification page section.
- Modify the available options as needed.
- Click Submit in the bottom right corner.
Customization via RWI
- Log in to the RWI.
- Click Branding. from the profile management section.
- To modify the hostname, update the customized data quality and ICANN registrant verification hostname and URL section as needed. Click Save.
- To modify the RV landing page, update the customize ICANN registrant verification page section as needed.
API
Two API commands are directly related to registrant verification.
get_registrant_verification_status |
The response provides the current state of the verification request for a domain. |
send_registrant_verification_email |
This triggers the verification email to the registrant when verification is required. |
63 Comments
Where can we set the registrant validation and reminder emails templates?
nevermind I found it
For anyone else who's looking to edit the templates, you can find them here: https://rr-n1-tor.opensrs.net/resellers/?action=msg_manage_templates
Received the first validation and would like to edit the exhibit a that is included in the messaging where can one do that. The renewal price found in it are not ours and are set at $50 that need adjusting .
Hi Greg,
We've removed the clause that included renewal and redemption pricing from the agreement.
That's Great Michael thanks for the quick action. First Client that received saw that and said "what $50 bucks"
Which nameservers are set for a suspended domain?
Miguel - when a domain name is suspended it is placed on ClientHold status, which stops the domain name from resolving. This is the same status the registry uses when a domain name expires for example. Validating the domain name immediately removes the ClientHold status.
Thanks Frank, now it's clear.
Hi,
When requesting the send/resend of the validation email does this send it instantly or is there a delay? Is this the same for suspended domains?
Thanks.
Hi Oliver - Thanks for checking. When you use the Resend email option in either the new control panel or via the API command the email with the validation link is sent out immediately.
I've got some questions.
Every time the registrant request an opt-in email resend . does the process timing restart from day 0?
Every time a mail change happened do the process start over again?
Does the domain change automatically its status into "verified" after corect verification in process? When one should have "admin-verifying" status ?
Hi Marco,
The process will not restart from day 0 every time a registrant requests a resend of the email.
Only if that email along with the first name and last name hasn't been previously verified.
Yes, once a domain is verified, it will show the status "Verified".
I think Marco meant 'admin_reviewing' status, which according to your docs (opensrs.com/docs/apidomains/Response_parameters_for_get_registrant_validation_status.htm) does exist.
Also this FAQ status the possible status as being 'Manual Review' not 'admin_reviewing', so which is it? Also the 2 API commands related to this do not appear in the Command List at http://opensrs.com/docs/apidomains/index.htm
In rare cases, some domains will require that our compliance team verify the contact information manually. When this happens, the status will be set to Manual Review (API: admin_reviewing).
My client is not receiving the verification email, though I have resent it through the control panel several times. How can I be sure the email is getting sent?
Hi Lauren - you can see the log of the email being sent in the Domain Notes for the domain. I've doublechecked the system and confirm the Validation emails are being sent out normally and arrive within 5 minutes at Gmail. If necessary, you can edit the Owner information in the new control panel to list a different email address for the client and then select the resend validation email from the Actions dropdown box on the top right to have a new validation email sent to the updated address.
The verification e-mail says....
To review and update your WHOIS contact information, please log into
our management interface at: https://manage.opensrs.net
If any of the information above is inaccurate, you should correct it.
If all of the information above is accurate, you do not need to take any action.
Please remember that under the terms of your registration agreement,
the provision of false WHOIS information can be grounds for cancellation
of your domain name registration.
If you have any questions or comments regarding ICANN's policy, please visit
the following link http://www.icann.org/registrars/wdrp.htm
...but doesn't say anything about the username and/or password. Where will registrants get their usernames and/or password from?
Well Eric in the same way as it has always occurred I would think You would have one of four option as I see it .
1 The owner use the user/pass they set up when registering as that is where the user pass comes from
You send it to them from the control panel link that been in the control panel since Opensrs started
you have a register user/pass form or system on your site they can request it.
they log in to their billing system such WHMC to get it
BOY OH BOY the OpenSRS resellers sure do like to complain as of late. Change is Change why not just embrace it and work with it . Its not all that difficult. And if you all really don't want to maybe stop selling something so darn complicated to deal with?
Thanks, reg.admin:
All of our OpenSRS customers have transferred their domains in to OpenSRS using WHMCS+OpenSRS Domains Pro module. I'll look in the customer area for the username/password feature.
Because it's a lot of extra damned work having to deal with poor planning. e.g., Why doesn't FAQ #2, "What exactly is the validation process?", match the page where registrants are actually sent? Why wasn't this process explained to resellers LONG before the change went into effect?
The link in the message takes visitors to a page that is COMPLETELY different than the one described (above).
We could ask the same of you. Couldn't we? Supporting small businesses (i.e., resellers) is going to be difficult. That's just the nature of the [wholesaling] beast.
Thanks, again!
Well Eric use the API that Opensrs provides, set up the forms as you need them to handle the issue that why its provided. OpenSRS supports the reseller in the best way I can imagine. We have never had an issue with any of their services its always stellar and they provide the tools needed to deal with any thing through the API. Its not just Opensrs having issue adapting resellers to this its all registry systems.
Thanks again, reg.admin:
Thoughts? Suggestions?
1, Eric user/pass is in the domain section copied below for example
being agitated about something you can do something about is well just not cool.............
| OpenSRS Username
|
|
| OpenSRS Password
|
|
Thanks, reg.admin:
I still don't see the OpenSRS Username & OpenSRS Password in the clients' domain area. Maybe this is a new feature for OpenSRS DomainsPro 1.1?
I can code (Perl & PHP) but there are only so many hours in a day and I've got a business to run [and cranky customers to support]. :P
Hey, Michael:
Rather than hash it out here [in the comments area, amongst everyone] I've submitted SR #214650. Please take a look and let me know if I've overlooked anything.
Eric
Eric Pretorious
Technical Operations Manager
Rocket-Powered.com
Hi Eric,
Since you are using WHMCS, your end users can update their contact details through your client area. This way they don't need a separate login and they don't have to visit manage.opensrs.net. WHMCS won't display the login details for that page anyhow.
If you do have any suggestions on how we can make this process easier, please let us know.
Thanks, Michael:
I don't see an option to verify the WDRP information through the clients' domain area of WHMCS (WHMCS, ver 5.2.15 + DomainsPro, ver. 1.0).
Is this a new feature of the OpenSRS DomainsPro, ver. 1.1?
Eric Pretorious
Technical Operations Manager
Rocket-Powered.com
FWIW, Michael:
I accidentally closed SR #214650 so I created a new SR: #214727.
Thanks, again!
Eric Pretorious
Technical Operations Manager
Rocket-Powered.com
Hi,
How to proceed with the registrant verification process if the domain name being suspended and prohibited to edit the email address while the current whois email is invalid.