.olayan
Generic top-level domain
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.olayan
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld olayanAdd --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 .olayan, 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 .olayan, 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. .olayan has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.nic.olayanFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.nic.olayan/domain/mybrand.olayan— a 404 means the name is free.
ds mybrand --tld olayan --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .olayan today. See Accuracy notes.
The registry
From IANA's delegation record for .olayan. .olayan is a generic TLD.
- Run by
- Competrol (Luxembourg) SarlBased in Luxembourg. Delegated 2016-04-21, record last updated 2024-05-31.
- Registry site
- www.olayan.comWhere the registry documents .olayan — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.nic.olayan · whois.nic.olayanWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.nic.olayanb.nic.olayanc.nic.olayanx.nic.olayany.nic.olayanz.nic.olayanThe 6 authoritative servers for the .olayan 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 .olayan was delegated to; this is what the root actually answers with when a resolver asks it where .olayan lives.
- Delegated to
a.nic.olayan37.209.192.92001:dcd:1::9b.nic.olayan37.209.194.92001:dcd:2::9c.nic.olayan37.209.196.92001:dcd:3::9x.nic.olayan156.154.172.822610:a1:1074::1:82y.nic.olayan156.154.173.822610:a1:1075::1:82z.nic.olayan156.154.174.822610:a1:1076::1:82
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 24340RSA/SHA-256 · SHA-256
84F7ADE4991F5338FC9612349A62C456810E645B4AF49B77AB8DD029ED8E5CEA
- key 24340RSA/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 olayan. NS and dig +norec @a.root-servers.net olayan. DS.