Ascio Web Service v3
NIS2 Registrant Verification
Registrant email address for domains that are under ICANN governed TLDs must be verified
Every registrant e-mail address must be verified. During this process an e-mail is sent to the registrant, the registrant clicks on a link, and his e-mail address is verified.Each e-mail address is only verified once.. If the registrant verification was already completed, it won't be sent again. The registrant verification process can be started before the order is submitted, via API or Portal. The verification status can be looked up in the portal: Domains > Registrant Verification. Possible order-statuses during the verification are:
- PENDING_VERIFICATION (still active)
| Operation | Day 1 | Day 7 | Day 15 | Day 30 |
|---|---|---|---|---|
| Register | Customer registers for a domain. An e-mail is sent out to the domain owner to be verified. Domain remains parked until verification | Second email verification sent 7 days after initial request. Domain remains parked until verification | Third email verification sent 15 days after initial request. | The registrant verification should be done until day 30. |
| Owner Change with documents | Domain has its e-mail address updated, or has an owner change. An e-mail is sent out to the domain owner to be verified. Domain remains active awaiting verification | Second email verification request sent 7 days after initial request. Domain remains active awaiting verification | Third email verification sent 15 days after initial request. | The registrant verification should be done until day 30. |
| Owner Change | Handled by the IRTP process. Since IRTP, Registrant Verification is not needed for Owner Changes without documents. The Registrant Verification is done during the IRTP. | |||
| Transfer | Registrant Verification email will be sent to the registrant email once transfer order is completed, if the registrant email is not already verified. | Second email verification request sent 7 days after initial request. Domain remains active awaiting verification | Third email verification sent 15 days after initial request. | The registrant verification should be done until day 30. |
How to integrate the Registrant Verification:
Ascio verification - We send e-mails to the registrant
- We send e-mail directly to your customer
- The partner adds our SPF record into the zone of the partners DNS-server. This is the SPF record:
v=spf1 ip4:212.123.41.224/28 include:_spf.hostedemail.com -all - With SPF record we can use the partners e-mail address as mail-from.
- We can create partner-templates with the partner language and text
- Please ask partnerservice for help.
You can provide us the mail-from, reply-to, subject-template, body-template and SPF. With that we can send mails and they look like yours. Here some examples:
- Registrant verification template #1
- Registrant verification template #2
- Registrant verification template #3
API-Verification - The partner sends e-mails and uploads them as a proof
- Before the customer registers a domain, the partner send the verification-mail to his customer (registrant)
- The partners uploads the e-mail via AWS. With that we can proof the the mail was sent.
- We won't send e-mails if the the partner has registrant-verification-mails deactivated in his account-settings.
- Please ask you integration specialist Manuel Lautenschlager for help
Use the API-verification method for these examples:
- You what to generate your individual mails with dynamic content
- You allready have a messaging-module and what to continue using it
- You have resellers as customer and you send the reminders for them
- Your company policy forces you to send your own e-mails
- You want you customized registrant verification confirmation website on your domain
Please click here for an example.
https://aws.demo.ascio.com/v3/aws.wsdl (OTE)
https://aws.ascio.com/v3/aws.wsdl (Live)
Please configure the IP-Whitelisting in the portal/demo-portal.