Domain Terms

1. Scope and precedence

These terms govern the contracting and management of domain names through Bacan, whether Bacan acts as registrar, reseller or technical intermediary before an accredited registrar.

By requesting a domain registration, transfer, renewal, restoration or data change, the customer accepts these terms, Bacan's conditions of use and the applicable policies of the registry, registrar, ICANN or competent authority for each extension.

In the event of conflict, these terms prevail over the general conditions only in relation to domain names.

2. Main roles

• Customer or registrant: the individual or legal entity in whose name the domain is registered.
• Registrar: the accredited entity that processes domain operations with the registry.
• Registry: the entity responsible for an extension, such as .com, .org, .es, .de or any other TLD.
• Administrative, technical or billing contact: the details associated with the domain when required by the extension.
• AuthCode or TAC: the authorization code required for many transfers.
• RDAP/WHOIS: public or restricted lookup services for registration data, according to applicable rules.

3. Availability, allocation and limits

Domain availability shown in a search is indicative until the registry confirms the allocation. Bacan does not guarantee that a specific name has been obtained until the relevant registry has accepted the operation.

Some domains may be reserved, blocked, subject to validation, protected by third-party rights, classified as premium or subject to local eligibility requirements.

• Bacan may reject operations that breach sector policies, applicable law or the acceptable use policy.
• The customer is responsible for checking that the requested domain does not infringe trademarks, trade names, image rights or other third-party rights.

4. Registrant data and checks

The customer must provide accurate, complete and up-to-date data. Inaccurate data or failure to respond to verification requests may result in suspension, blocking, cancellation or loss of the domain.

Bacan may request verification of email address, identity document, address, company ownership or extension-specific eligibility where required by applicable policies or where there is a reasonable risk of fraud.

• The customer authorizes the transfer of the necessary data to registrars, registries, ICANN, authorities or technical providers involved in the operation.
• Domain privacy will apply where the extension and registrar allow it.
• Some data may appear in RDAP/WHOIS according to applicable regulations and policies.

5. Registration, renewal and expiry

Domains may be registered for the periods allowed by each extension. Renewal may be carried out manually or through automatic renewal where enabled and payment is successful.

Expiry notices are an operational aid, but the customer remains ultimately responsible for monitoring expiry dates and confirming that the domain has been renewed.

• After expiry, the domain may enter grace, redemption or deletion periods, with deadlines that vary depending on the extension.
• Restoration during a redemption period, where available, may involve additional non-refundable fees.
• The customer must report any renewal incident as soon as it is detected and, in any case, within ten calendar days after the expiry date.

6. Transfers and registrant changes

Transfers may require the domain to be unlocked, an AuthCode, email confirmations, registrant validation and the absence of blocks imposed by registry or registrar policies.

A registrant change or a change to relevant data may trigger additional checks and, for some extensions, temporary transfer locks.

• Bacan will not unduly block an outgoing transfer where the customer is up to date with payments and there is no legal, contractual or technical impediment.
• The customer warrants that they have sufficient authorization to request changes to the domain.

7. DNS, nameservers and security

The customer is responsible for the DNS configuration they apply, for its technical effects and for keeping operational emergency contacts.

Bacan may intervene proportionately in the event of serious security incidents, abuse, phishing, malware, authority requests or risks to platform stability.

• We recommend enabling transfer lock except when the domain is about to be transferred.
• We recommend using a contact email address that does not depend on the domain itself.
• DNSSEC should only be configured where the DNS provider and the extension support it correctly.

8. Prices, payments and refunds

Prices for registration, renewal, transfer, registrant change, restoration or complementary services may vary by extension, provider, currency, taxes or registry decisions.

Domains are specific execution services and, once the operation has been processed with the registry or registrar, they are non-refundable unless there is an error attributable to Bacan that cannot be corrected.

• Premium domains may have higher prices for registration, renewal or transfer.
• Restoration, verification or eligibility fees will be charged where applicable.
• Non-payment, chargeback or suspected fraud may lead to suspension of services linked to the domain while the situation is regularized.

9. Disputes, trademarks and authorities

The customer agrees to be subject to the dispute resolution procedures applicable to each extension, including UDRP, URS, national registry policies or decisions by competent authorities.

Bacan may implement final decisions for transfer, cancellation, suspension or blocking notified through recognized channels.

10. Liability

Bacan will act with reasonable professional diligence, but is not responsible for delays, rejections or incidents caused by registries, registrars, third-party checks, errors in data provided by the customer or the real availability of the domain.

Bacan's total liability for a proven and attributable domain-related incident shall be limited, at most, to the amount paid for the affected operation, excluding loss of profit, loss of business, reputation or indirect damages.

11. Changes

Bacan may update these terms due to legal, technical, operational or sector policy changes. The current version will be published on this page.