This Appendix forms part of the Domain Name Agreement.
1. General rule
Each registry or registrar may impose specific conditions for registration, transfer, trade or change of holder, renewal, DNS or verification. Requirements may change without Domain Market having an opportunity to review them in advance.
The Customer agrees to provide the information, declarations, acceptances and supporting documents required by the registry or registrar at the time of the transaction and displayed at checkout, in the Custom Client Area or in a later verification request.
2. Types of additional requirements
Requirements may include, for example: an identity card or passport; a personal or tax identification number; VAT or company registration number; a certificate of incorporation or other company document; proof of address; country of citizenship, residence or registered office; local presence or a contact for service of documents; a trademark or right to a name; an intended-use or eligibility declaration; specific acceptance of registry terms; email or phone verification; correctly preconfigured authoritative nameservers; and additional administrative or technical contacts.
3. TLDs with known special procedures or additional information requirements
The following list is an operational guide, not a fixed technical specification. The registry or registrar’s response takes precedence.
.eu / .ευ / .ею — EU/EEA eligibility or citizenship criteria apply where provided for. EURid may initiate verification and request supporting evidence.
.de — Compatible, preconfigured nameservers are required. Identity or risk-based verification may apply. In a legal dispute, a holder outside Germany may need to appoint a person in Germany to receive official documents in accordance with DENIC’s rules.
.it — The registry’s eligibility and geographic requirements apply. Individuals and companies must provide specific identification, tax or company details and configure DNS correctly. The exact fields are displayed when placing the order.
.es — Additional identification information is required for individuals or companies, together with acceptance of the registry terms in force. The registry may request supporting documents to verify the information.
.se / .nu — Individuals must provide a personal identification number or ID, and legal entities an organisation or company registration number, together with any required acceptance of registry policies.
.us — A nexus and purpose declaration and additional eligibility information are required under .US rules. Incorrect information may lead to revocation.
.pt — Full identification details are required, together with tax or VAT information depending on the holder type. Evidence or compliance verification may be requested. Nameservers must meet registry requirements.
.bg — Applications may require enhanced identification or company evidence and supporting documents, depending on the holder or name category. The registry or registrar determines the fields and documents currently required.
.cy / .com.cy — The Cypriot registry’s specific rules, eligibility criteria and category limits apply. Information or supporting documents concerning the applicant and the name may be requested.
.hu — Specific eligibility and contact requirements apply, and additional information or declarations may be needed. The exact requirements are obtained dynamically from the registrar or registry.
.dk — A specific registry process applies to validation, activation and verification of the holder’s details under the .DK model.
.fr — AFNIC eligibility and verification rules may apply, including requests for documents where details cannot be verified automatically.
.at — The registry may initiate verification of the holder’s details. Unsuccessful verification may lead to revocation of the domain.
.fi / ee / is / lt / lv / pl / ro / rs / si / sk — These European ccTLDs have registry-specific contact, identity, DNS, transfer or verification requirements. Checkout must dynamically request the additional fields returned by the registrar.
.cn — Real-name identification or company details and registry verification may be required. Registration or activation depends on successful verification.
.hk — Identification or company details and supporting documents may be required, depending on the holder category.
.in — Additional registrant data and compliance with .IN registry rules may be required.
.id — .ID categories may have eligibility or document requirements depending on the second-level extension. The service is provided only where the applicable rules are met.
.ae — .aeDA-specific holder information and verification requirements apply.
.ma — An identification number may be required for individuals, or a company registration number for legal entities.
.dm — The registry may require the holder’s personal email address rather than generic addresses such as admin@ or contact@.
.ru — More extensive identification data may be required for individuals or companies. Domain Market may request additional information before submission.
.ae.org / gr.com / other third-level or CentralNic zones — The registry operator’s specific rules apply. Additional fields or specific acceptance of terms may be required.
4. Further TLDs subject to dynamic validation
For the following TLDs available in the Domain Market catalogue, checkout must check additional-data and eligibility requirements with the relevant registrar before the order is completed:
.ac, .ae, .af, .ag, .ai, .al, .am, .as, .at, .ax, .ba, .be, .bg, .bo, .by, .cd, .cf, .cg, .ch, .ci, .cm, .cn, .com.cy, .cr, .cy, .cz, .de, .dk, .dm, .do, .ec, .ee, .es, .eu, .fi, .fo, .fr, .ga, .gd, .ge, .gf, .gg, .gl, .gp, .gq, .gs, .gy, .hk, .hn, .hr, .hu, .id, .im, .in, .ir, .is, .it, .ke, .kz, .li, .lt, .lu, .lv, .mk, .mu, .mx, .nl, .pl, .pt, .ro, .rs, .ru, .sc, .se, .si, .sk, .sx, .uk, .us.
A TLD’s inclusion in this list does not mean that documents are always required. It means that the specific registry or registrar rules must be checked dynamically and shown to the Customer before or after submission, depending on the registry’s process.
5. Verification after registration
A registry may request verification even after successful registration. The Customer must respond within the registry’s deadline. Domain Market is not liable for suspension or revocation caused by inaccurate information or the holder’s failure to respond.
6. Rejection and refunds
If a registry rejects an application before an irreversible charge is incurred, Domain Market refunds the amount for the transaction not provided. If the registry or registrar transaction has already been carried out or charged irreversibly, the non-refundability rules in the Domain Name Agreement apply, unless the law requires otherwise.
7. Changes to registry rules
Domain Market may update this Appendix and checkout fields without revising the entire Domain Name Agreement when a mandatory technical or verification rule of a registry or registrar changes.