Domain Policy

01Provider and policy scope

A domain order must identify the sponsoring registrar, relevant registry, applicable registration agreement and any TLD-specific eligibility rules. Weeby is not represented by this theme as an ICANN-accredited registrar. A live operator must disclose whether it acts as a registrar or reseller.

ICANN consensus policies apply to covered generic top-level domains through the relevant contracts. Country-code and sponsored domains can have different requirements. A live customer must be able to review the terms applicable to the selected extension before approval.

02Availability and registration

A domain search or price display is not a reservation. Registration is complete only after the registry accepts the transaction and the provider confirms it. Another party may register a name between a search and final submission.

You are responsible for selecting a name that you may lawfully use and for satisfying any extension-specific requirements. An available registration does not establish trademark rights or permission to use another organisation’s identity.

The live order must disclose registration, renewal, transfer, premium-name, restoration and other material fees. Promotional first-year pricing should be distinguished from the renewal price. The WHMCS domain-order flow uses the lookup and registrar modules enabled by the operator. Displayed availability and transaction completion depend on those configured providers and their responses.

03Registration details and verification

Provide accurate registration information and a working contact address. Keep the account secure and update details promptly when they change. The sponsoring registrar may require verification, supporting information or a response to a registration-data enquiry.

The applicable agreement must explain the consequences of missing required verification or providing inaccurate data. Registration information is handled under the relevant Privacy notice, registrar or registry terms and applicable registration-data rules.

Privacy or proxy options, if available for the extension, must state their scope and limitations. They do not eliminate lawful disclosure, dispute or validation requirements.

04Renewals and expiration

Monitor the registration term and maintain current contact and payment information. Auto-renewal is a payment and renewal instruction, not an unconditional guarantee that the registry will accept a renewal.

For covered gTLD registrations, ICANN’s expiration policy requires notices around one month and one week before expiry, with an additional notice within five days after expiry where the registration remains unrenewed or undeleted. The live operator must explain the actual notice channel and destination.

Expiration can interrupt DNS, websites and email. Post-expiry renewal, deletion and restoration depend on the applicable registration state and rules. Do not assume that the service remains available or that an expired name is held indefinitely.

Eligible deleted gTLDs generally have a 30-day redemption period, subject to policy exceptions. Restoration must be requested through the relevant registrar and may incur a disclosed fee. Other extensions can follow a different lifecycle.

05Transfers and changes of holder

A registrar transfer is different from changing nameservers, moving website files, changing the account contact or transferring the registration to another holder. Confirm which action you want before submitting a request.

Transfers require proper authority and compliance with the applicable policy. Locks, registration state, recent registration or transfer, a change of registrant, an active dispute or a court direction can affect eligibility. The sponsoring registrar must explain the relevant process and any lawful reason for denial.

Keep authorisation codes secure, verify the receiving registrar and follow the required confirmations. Do not disclose a transfer code in a public ticket, ordinary enquiry or screenshot. No universal completion time is promised by this model policy.

06DNS and related services

Domain registration and hosting are separate services. Changing nameservers or DNS records can affect websites, mail delivery, validation and other applications. Review the current records and retain a copy before making changes.

DNS updates are subject to caching and the relevant configuration. A transfer does not automatically migrate a website, copy mailboxes, preserve all DNS records or cancel the old provider’s services.

If the provider manages DNS, DNSSEC or an associated privacy service, the order must specify the scope and any dependency on the registration or hosting subscription.

07Rights, disputes and abuse

You remain responsible for lawful use of a name and for responding to applicable rights-protection, abuse and legal processes. Covered disputes may involve ICANN policies such as the UDRP, while other extensions may use their own procedures.

A registrar, registry or competent authority may require a lock, suspension, cancellation or transfer under the applicable agreement, policy or law. No registration service can promise immunity from these processes.

Abuse reports and ownership claims should identify the name and the relevant evidence without disclosing unnecessary sensitive information. The live provider must publish the appropriate reporting route.

08Cancellation, refunds and customer help

Completed registry transactions can be irreversible. Any voluntary cancellation or refund window depends on the extension, transaction, stage and accepted terms; it is separate from mandatory legal rights and correction of provider errors. See the Refund & cancellation policy.

Deleting a name, disabling auto-renewal and transferring to another registrar have different consequences. Confirm the requested action and retain written confirmation. Do not cancel a related hosting or email service until the required migration and access checks are complete.

Use the domain registration flow, transfer flow or the authenticated domain account pages for the relevant action. The operator must configure supported extensions, registrar modules and permissions; submitting a request does not itself confirm registry completion.