Specific domain terms

1. Purpose and parties involved

1.1. These terms govern domain name registrations, renewals, transfers and other operations purchased through WebMonster. They supplement the General terms and conditions and the accepted order.

1.2. WebMonster processes domain operations through its registrar, Hosting Concepts B.V., operating as Registrar.eu. Each extension’s registry administers domains with that extension; the registrar submits operations to that registry.

1.3. The domain registrant is the person or entity identified as such in the registration data. This may differ from the Customer placing the order or paying the invoice. A Customer acting for another person or entity must have sufficient authority to request the operation and accept the relevant terms on their behalf.

1.4. Registration gives the registrant a right to use the domain for the registered period, subject to the extension’s rules. It does not confer rights over others’ trademarks, trade names or other signs. The Customer must check that the requested name and its use do not infringe third-party rights.

2. Registry rules and acceptance for .es domains

2.1. By accepting the General terms and conditions for an order including a domain, the Customer accepts these specific terms and the registrar’s and relevant registry’s terms expressly identified and linked in this document, in the version accessible before purchase and only insofar as applicable to the order. These include the Registrar.eu Registration Agreement for registrants. Linked documents may be viewed and retained before purchase. This incorporation does not replace any specific acceptance required by the registry or registrar.

2.2. Generic domains subject to ICANN are governed by its applicable registration, transfer and dispute resolution policies. Country-code domains, such as .es or .eu, are governed by their respective registries’ rules. Rules for one extension do not automatically extend to all others. Changes affecting the service will be communicated according to applicable obligations; WebMonster’s own changes are governed by the general terms.

2.3. For .es applications, including applicable third-level domains, Red.es Annex III (PDF) forms part of these terms. The applicant accepts its declarations and authorisations, .es allocation rules and Red.es procedures applicable to the operation. The annex must be made available before acceptance.

2.4. Through that acceptance, the applicant authorises Hosting Concepts B.V., under the name Registrar.eu, as registrar for the actions before Red.es described in the annex. WebMonster will process the Customer’s instructions through that registrar.

2.5. Acceptance must come from the registrant or a person with sufficient representative authority. WebMonster will retain evidence of acceptance and the version supplied, and may request evidence of authority where necessary. Merely paying for someone else’s domain does not establish that authority.

3. Application and registration

3.1. Before confirming the order, the Customer must check the full name, extension, registrant and requested period. Availability searches do not reserve a domain. Allocation depends on the registry accepting and completing the operation.

3.2. WebMonster will start processing once payment and necessary data, authorisations and checks have been received or completed. It will explain special requirements for the extension and expected timescales. The registry may require further documents or reject an application that does not meet its rules.

3.3. If the purchased registration or transfer cannot be completed, WebMonster will inform the Customer and refund that operation’s price without undue delay. It will not substitute another domain without the Customer’s acceptance.

3.4. Once registered, changing the name or extension usually requires buying another domain. If the Customer confirmed an incorrect name, correction depends on registry capabilities, and any cost will be disclosed in advance. This does not exclude correction or refunds due for an error attributable to WebMonster.

4. Registrant details and verification

4.1. The Customer will provide genuine, complete and up-to-date registrant and contact details required by the extension, including applicable identification documents. They will report changes promptly and respond to verification requests within the stated period. WebMonster will not replace unknown mandatory information with fictitious details.

4.2. The registrar or registry may contact the registrant or their contacts directly to verify data, approve operations or warn of issues and expiry dates. The Customer must keep those channels operational and cooperate with checks. WebMonster will relay relevant requests it receives that require the Customer’s involvement.

4.3. False or outdated data, or failure to respond to verification, may prevent an operation or lead to domain suspension or cancellation under applicable rules and deadlines. The cause and available remedies will be communicated where appropriate. Domain suspension may interrupt the website, email and other dependent services.

4.4. A change of registrant or contact details may require additional authorisations or trigger a temporary transfer restriction. WebMonster will explain applicable consequences before processing where they can be known. Not every data change triggers the same lock, and not all extensions have the same periods.

5. Duration, price and renewal

5.1. The order identifies the purchased period and price. The registration expiry date is the date recorded by the registry. WebMonster’s renewal and payment date is brought forward where provider deadlines require it. These dates may differ.

5.2. Renewal is automatic while enabled under the contract. WebMonster will request payment on the communicated renewal due date, unless it has received a timely non-renewal request. Issuing an invoice earlier does not, by itself, bring forward the automatic charge.

5.3. Receipt of payment triggers immediate renewal processing. If the Customer pays manually before the due date, processing begins then, without waiting for the automatic charge date. This effect will be explained before advance payment is confirmed. The new expiry date and added period depend on extension rules and domain status.

5.4. Notices will identify the domain, renewal price, planned charge date and deadline to avoid renewal. General-term notice periods and additional notices required of the registrar or registry will be respected. The Customer must keep contact and payment details current; WebMonster retains its own information and diligent-processing obligations.

5.5. Price revisions will be notified under the general terms. Special-price or premium domains may have registration and renewal rates different from standard rates, which must be identified before the relevant purchase. Restoring an expired domain or other exceptional operations requires prior disclosure and acceptance of the cost.

6. Non-renewal, expiry and recovery

6.1. To avoid renewal, the Customer must disable automatic renewal using the relevant customer-area button, effective immediately without manual approval. Alternatively, they may open a support request identifying the domain. The deadlines and effects in section 7.2 of the general terms apply, including 72 working hours’ notice for manual processing of a support request. Manual advance payment is subject to section 5.3.

6.2. Disabling automatic renewal does not retroactively cancel an operation already completed. Non-renewal allows the domain to reach the end of its registered period and does not itself request immediate deletion. If the registrant expressly requests early deletion, the procedure and consequences will be explained according to registry capabilities.

6.3. If payment is not received in time, the domain may expire and stop working. No general thirty-day retention period for non-payment applies to domains: continuity and recovery depend on the relevant registry’s rules and status.

6.4. Where a late-renewal or recovery period exists, WebMonster will explain options, the available deadline and applicable price. Possibilities differ by extension. A late request does not guarantee recovery; WebMonster will diligently process any operation it agrees to undertake.

6.5. Once released, a domain may become available to third parties. Recovering or re-registering it does not itself recover a website, emails or other data deleted from separate services.

7. Transfers and registrant changes

7.1. A transfer changes the registrar managing the domain. It does not necessarily change its registrant, DNS servers, web hosting or email provider. Those other operations must be requested or configured where needed.

7.2. For an incoming transfer, the Customer will provide authorisations and, where applicable, a transfer code and an unlocked domain. The price and whether a registration period is added will be explained before purchase. The process may require registrant confirmations and may be subject to locks, disputes or registry restrictions.

7.3. For an outgoing transfer, WebMonster will provide the code or carry out its required actions after proportionate verification of the requester’s authority and within applicable deadlines. Any refusal or lock must have grounds permitted by the extension’s rules and will be communicated with available remedies.

7.4. Starting a transfer does not mean it is complete or, by itself, stop a pending renewal. A Customer who does not want to renew with WebMonster must request non-renewal before it is carried out and plan the transfer around registry timescales. Once the outgoing transfer is complete, WebMonster will stop processing future renewals for that domain.

7.5. Registrant changes require the relevant parties’ authorisation and the extension’s procedure. Changing billing or WebMonster account details does not itself change the registered holder.

8. DNS and domain parking

8.1. The Customer may configure DNS records through the management options included in their service. They must check changes, as incorrect settings can affect the website, email and other features. Changes becoming visible online also depend on caches and providers involved, so are not always immediate.

8.2. Domains include free parking through a customisable default page or a redirect, under the parking section of the Specific hosting terms. This does not include a web hosting plan or email mailboxes.

8.3. Before changing registrar or DNS servers, the Customer must coordinate the configuration needed to preserve services that depend on the domain. WebMonster will provide the information and assistance included in its service. Purchasing or cancelling a domain does not automatically change independent hosting, email or Managed subscriptions.

9. Personal data and public lookups

9.1. WebMonster will process data necessary to manage the purchase and disclose to the registrar and registry the data required to process and maintain the domain. Entities determining their own registration purposes and obligations act as controllers for that processing. The Privacy policy and registrar and registry information identify the processing and corresponding rights.

9.2. Information accessible through public registration lookups, such as RDAP or WHOIS, depends on the extension, registrant type and applicable law. It is not assumed that all personal data is public or that purchasing a domain authorises full publication. Any additional privacy services will be expressly described when offered.

9.3. Customers providing other people’s data must inform them and have the necessary legal basis and authorisations. Accepting these terms neither replaces that obligation nor permits advertising uses unrelated to the purchase. Exercising data protection rights is not conditional on giving up the domain, without prejudice to data lawfully needed or retained to maintain it.

10. Use, disputes and liability

10.1. Domains must be used lawfully, respecting general acceptable-use obligations and the extension’s rules. Fraud, impersonation, phishing, malware distribution and infringement of third-party rights are prohibited.

10.2. A domain may be suspended, cancelled, locked or transferred where required by a competent decision or applicable registry or registrar procedures. Name disputes are governed by the system applicable to the extension. Claims against WebMonster for its own service retain the channels and rights provided by the general terms and law.

10.3. WebMonster will communicate significant incidents and measures of which it becomes aware unless legally prohibited, and explain actions available to the Customer. Registry or registrar involvement does not remove WebMonster’s liability for its own breaches.

10.4. Domains do not carry the commercial thirty-day money-back guarantee in the general terms. A properly completed operation is not undone simply because the Customer decides to stop using the domain. Applicable consumer withdrawal rights and rights to refunds or compensation for breach remain under the general terms. Registration, transfer or renewal does not automatically exclude those rights merely because it was paid for or requested.

10.5. Liability and its limits are governed by the general terms. Hosting or email availability commitments do not, in themselves, extend to domain registration.