.ovh
Generic top-level domain
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- RDAP + WHOISanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.ovh
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld ovhAdd --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.
What it costs
No registrar in the price table bundled with ds quotes .ovh, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.
Who can register
No eligibility rule is on file for .ovh, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .ovh has both, so RDAP answers and WHOIS is the fallback if it does not.
- RDAP
https://rdap.nic.ovhFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.nic.ovh/domain/mybrand.ovh— a 404 means the name is free.- WHOIS
whois.nic.ovhQueried on port 43, from the bundled whois.json. The name is called free when the reply containsnot found— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld ovh --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .ovh today. See Accuracy notes.
The registry
From IANA's delegation record for .ovh. .ovh is a generic TLD.
- Run by
- OVH SASBased in France. ICANN records the contracted registry operator as MédiaBC. Delegated 2014-05-01, record last updated 2026-08-05.
- Registry site
- www.ovh.comWhere the registry documents .ovh — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.nic.ovh · whois.nic.ovhWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
d.nic.frf.ext.nic.frg.ext.nic.frThe 3 authoritative servers for the .ovh zone — what the root delegates to. Nothingdsqueries directly; they are what makes a registered name resolve.
What it is
Derived from the root zone and ICANN's registry list — each one is a fact with a source.
genericIANA Root Zone Database types it "generic"new-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
In the root zone
The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .ovh was delegated to; this is what the root actually answers with when a resolver asks it where .ovh lives.
- Delegated to
d.nic.fr194.0.9.12001:678:c::1f.ext.nic.fr194.146.106.462001:67c:1010:11::53g.ext.nic.fr194.0.36.12001:678:4c::1
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 51966ECDSA P-256/SHA-256 · SHA-256
CA942C4051CFFD445F83DEE1AC0A94E67C0A59E549F2981D4A243D16F2C98F2B
- key 51966ECDSA P-256/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net ovh. NS and dig +norec @a.root-servers.net ovh. DS.