Buying a domain name from OVH involves choosing an extension, configuring a DNS zone, and understanding the locks that apply from the moment of creation. Before finalizing the order, several technical parameters should be compared to avoid future issues, particularly regarding transfer times and default protection settings.
Comparison of OVH domain extensions: price, usage, and constraints
The choice of an extension determines both the positioning of the site and the administrative rules that will apply throughout the ownership period. Not all extensions are equal in terms of availability, renewal conditions, or geographical restrictions.
| Extension | Main Usage | Geographical Restriction | ICANN Transfer (post-creation delay) |
|---|---|---|---|
| .com | International commercial site | None | 60 days mandatory |
| .fr | Site targeting France | Holder in the EU or Switzerland | AFNIC rules (distinct from ICANN) |
| .net | Technical projects, networks | None | 60 days mandatory |
| .org | Associations, NGOs | None | 60 days mandatory |
| Local extensions (.paris, .bzh) | Territorial anchoring | Variable depending on the registry | Variable |
For extensions governed by ICANN (.com, .net, .org), a domain cannot be transferred for 60 days after creation or a change of ownership. This rule, imposed by ICANN and enforced by OVHcloud, prohibits any quick corrections if the chosen registrar is not suitable.
Before confirming a purchase, it is advisable to check if the project will require a short-term transfer. A site launch planned in the following weeks leaves no room for migrating to another provider.
Transfer Protection and OVH Authorization Code
OVHcloud automatically activates a protection against outgoing transfers (clientTransferProhibited status) on each domain subject to ICANN rules. This lock prevents any unsolicited transfer, but it also imposes a specific procedure when the owner wishes to change registrars.
When deciding to transfer a domain, the first step is to disable this protection from the OVH customer area, then retrieve the authorization code (auth code). This code has a limited validity period: after seven days, the protection automatically reactivates, and the code becomes invalid.
- Disable the transfer lock in the “General Information” tab of the relevant domain
- Retrieve the authorization code immediately after deactivation
- Initiate the procedure with the new registrar right away, without waiting several days
- Ensure that the domain has exceeded the 60-day post-creation period before any attempt
The operational window is therefore short. Preparing the account with the target registrar before disabling the protection helps avoid wasting the code and having to restart the procedure.
To better understand the preliminary steps and available options, it is useful to refer to resources that detail how to buy a domain from OVH while considering these technical constraints.
OVH DNS Zone: Records to Configure After Purchase
Buying the domain is not enough to make a site accessible. The associated DNS zone must contain the correct records to direct traffic to the hosting server, whether it is with OVH or elsewhere.
An A record links the domain name to the IP address of the server. If the site is hosted with a third-party provider, the default A record must be replaced with the IP provided by that host. A CNAME record may also be necessary for the “www” subdomain.
For email usage, MX records must point to the mail server. OVH preconfigures these entries when mail hosting is subscribed to at the same time as the domain. However, if the email is managed by an external service, the default MX records must be modified manually.
A common pitfall concerns the TTL (Time To Live). After a DNS zone modification, propagation can take several hours. Modifying an A record the day before a site launch creates a risk of temporary unavailability. Anticipating DNS changes at least 48 hours before going live remains the most reliable precaution.
OVH Redemption Phase: Recovering an Expired Domain
A domain not renewed in time does not disappear immediately. After expiration, it enters a redemption phase during which recovery remains technically possible but at a significantly higher cost than standard renewal.
Redemption fees vary by extension and far exceed the annual price of the domain. For a .com or .net, these fees can represent several times the cost of standard renewal. The original owner retains priority during this phase, but once it is over, the domain is released and anyone can register it.
- Enable automatic renewal in the customer area to avoid any accidental expiration
- Ensure that the payment method associated with the OVH account is valid and up to date
- Monitor reminder emails sent by OVH before the deadline
Losing a domain that bears the name of an active brand or project generates consequences far beyond the simple cost of repurchase: loss of SEO, undelivered emails, broken inbound links. Automatic renewal is the only truly effective safety net.
The most underestimated factor when purchasing an OVH domain is not the initial price or the choice of extension. It is the combination of the 60-day transfer lock and the 7-day window to use the authorization code that creates the most blocking situations. Planning for these constraints right from the order avoids unpleasant surprises several months later.