Fairverra Domain Registration Agreement

This agreement is between the Fairverra account holder and Fairverra (operated by Nuevo Comienzo BV, the Netherlands). It applies to each domain the account registers, transfers in, renews or restores.

A domain under this agreement is sponsored by a registrar. The registrar may change. Fairverra is the registration company on this agreement and contracts with the account holder in its own name. Fairverra is not the registrar and is not ICANN-accredited. On request we identify the registrar that sponsors the domain at that time. You can also look up a gTLD registrar via ICANN Lookup.

Acceptance is by the account. An API key the account holder authorized is enough, including a key used by an AI agent. That acceptance binds the account holder. Fairverra does not ask the registrant for a separate click. A registry or ICANN policy that describes such a click does not add one to this agreement.

If the registrant contact is the account holder, the account holder accepts as the registrant. If the registrant is your customer, you accept for them and you make them follow this agreement. That is your responsibility. Fairverra does not contract with your customer, does not check that you did this, and is not liable to them or to you for what they do or fail to do. The registrant named in the handle is the domain holder towards the registry. You remain the customer who pays Fairverra.

Each registration is subject to the policies of the registry for that TLD and, for gTLDs, to ICANN policies. Those include, where they apply, the Uniform Domain-Name Dispute-Resolution Policy (UDRP), the Uniform Rapid Suspension procedure (URS) and the Transfer Policy. ccTLD registries impose their own rules. You comply with a formal decision about a domain, such as a panel decision or a court order, and you cooperate in a legal process about a domain under the account.

For gTLDs this agreement is the registration agreement for the domain. We keep a record of it, cooperate in disputes, provide authorization codes and unlocks where the TLD uses them, and inform you about deletion and auto-renewal. We identify the sponsoring registrar when you ask.

See also ICANN's Registrants' Benefits and Responsibilities and Registrant Rights and Responsibilities.

You submit accurate, complete registrant data and keep it current. A willful inaccuracy is a ground for suspension or cancellation by the registry or registrar. Changes to the holder's details are sent to us without delay. The account holder is responsible for data submitted through the API, including data submitted by an agent.

Some TLDs require extra data (company registration, a local presence, a specific contact role). The API returns those requirements per extension. An order that does not meet them fails at confirmation.

You choose the domain name. You check that it does not infringe someone else's rights. Fairverra and the registrar do not review trademark clearance. You indemnify Fairverra against claims that arise from the name or from how the domain is used.

We may suspend a domain immediately, without telling the account first, including on an abuse report, a court order, or a dispute decision.

The order is for the period in the quote (registrations through the API are for one year). Renewal is a separate order unless auto-renew is on for that domain. Auto-renew is off by default. You can always choose not to renew. Fairverra sets the price and may change it at any time, including when the registrar's price has not changed, as the Terms of Service describe. A price in an email is a price at the moment of sending. It can change, and no rights can be derived from it.

After expiry the domain follows that registry's process. Periods, fees and whether a restore is still possible differ per TLD. We do not promise a fixed number of recovery days. A restore quote shows the fee. If the registry refuses the restore, section 3 of the Terms of Service applies to a confirmed failure.

Expiry and renewal notices may come from Fairverra or from another party, including the registrar, the registry, or a partner. You can turn off Fairverra's mail to the account. That does not stop a notice sent by someone else.

You watch the expiry date yourself, as section 5 of the Terms of Service says. If you register for your own customer, you make them watch their expiry date too. A missed Fairverra mail is not a claim against Fairverra.

Outgoing transfers follow the applicable ICANN, registry and registrar policy. We do not promise that every domain can leave at any moment. Where the TLD uses an authorization code, the account holder can retrieve it. Where the TLD supports a registrar lock, the account holder can unlock. We do both within five calendar days of the request where those mechanisms exist. Some TLDs have neither.

Where a policy requires approval of a transfer or a change of registrant, you authorize Fairverra, and through Fairverra the registrar, to submit that approval for domains on the account. If the registrant is your customer, you give that authorization for them and you are responsible for having their permission. This does not override a lock, a dispute, or a registry rule that forbids the transfer.

For each domain order we keep the account's acceptance of this version, the order (domain name, registrant handle, time), and this text. We keep that record until at least two years after the account or the domain relationship ends. The registrar may ask for a copy.

If you resell, you keep the equivalent record for your own customer, as section 7 of the Terms of Service requires. Your customer's failure to pay you does not cancel this agreement or the wallet charge.

We may update this agreement on its own, without updating the Terms of Service. A new version must be accepted before the next production deposit or paid API order, as the Terms of Service describe.

Payment, quotes, wallet credits, liability and account termination are in the Terms of Service. Personal data is described in the Privacy Policy. If a registry rule conflicts with this agreement, the registry rule wins for that TLD.

Dutch law applies, on the same terms as the Terms of Service.