Domain Registration Data Accuracy and Verification Policy

AIvikings provides domain name registration services and maintains a database of domain name registration data. This policy describes the procedures we use to keep that data accurate and complete, as required by Article 28 of Directive (EU) 2022/2555 (NIS-2). We publish it so that registrants and legitimate access seekers can understand how we meet that obligation.

Registration data we collect

For each domain registered through AIvikings, we collect and maintain the registration data required by ICANN policy, registry rules, and NIS-2, which may include: - Registrant name - Registrant email address - Registrant postal address - Registrant telephone number - The domain name, its registration and expiry dates, and the sponsoring registrar and registry

We collect this data at the point of registration, whether the registration is made through the web interface, the REST API, or the MCP server, and whether it is initiated by a person or by an automated agent.

Verification procedures

Email verification. Before a contact can be used as registrant contact data, the associated email address must be verified. We verify it by sending a one-time code to the address and requiring that code to be entered back. Verification is subject to attempt limits and rate limiting. An email address that has not been verified cannot be used as registrant contact data.

Verified contact handles. A verified contact is stored as a reusable contact handle on the account. Registrations reference a verified contact handle rather than raw, unverified contact details, so the human verification step is completed once when the contact is established and is not repeated for every domain.

Automated and agent registrations. Automated and agent-driven registration is supported. An automated agent may register a domain only by using a verified contact handle; the registration interface does not accept unverified raw contact details from an agent. This keeps registrant data verifiable even where no human is present at the moment of registration.

Keeping data accurate and current

You are responsible for providing accurate and complete registrant contact data and for keeping it current. If your details change, you must update them in your account. Where we become aware that registrant data is inaccurate, incomplete, or cannot be verified, we may ask you to correct or re-verify it within a reasonable period.

Consequences of inaccurate or unverified data

Where required registrant data is missing, inaccurate, or unverified and is not corrected or verified on request, we may suspend or lock the affected domain, in line with our Registry Policies and Terms and Conditions, and as required by ICANN policy, registry rules, and NIS-2. We may act without prior notice where a registry, ICANN policy, or law requires it.

Publication and disclosure

Non-personal registration data is published in public directories (WHOIS / RDAP) by the relevant registry, with personal registrant contact data redacted by default in line with GDPR and registry policy. Disclosure of non-public registration data to authorities and to other legitimate access seekers is handled under our NIS-2 Disclosure Procedure and Third-Party Data Request Procedure.

Our role and cooperation

AIvikings provides domain registration services as a reseller operating under the ICANN accreditation of our upstream accredited registrar partner. Registration data we collect and verify is passed to that partner and to the relevant registry. We cooperate with our upstream accredited registrar partner and the relevant registries to avoid duplicating the collection of the same data, consistent with Article 28 of NIS-2.

Contact

Questions about this policy: hello@aivikings.ai