.كوم.xn--fhbei

Internationalised top-level domain

RDAP + WHOIS

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.كوم

Check a name

One command, straight against the registry — no account, no page to load.

Name

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld xn--fhbei

Add --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 .كوم, 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 .كوم, 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. .كوم has both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP: https://tld-rdap.verisign.com/xn--fhbei/v1From IANA's bootstrap, refreshed when this page was built. The lookup is https://tld-rdap.verisign.com/xn--fhbei/v1/domain/mybrand.xn--fhbei — a 404 means the name is free.
WHOIS: whois.nic.xn--fhbeiQueried on port 43, from the bundled whois.json. The name is called free when the reply contains no match for — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld xn--fhbei --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .كوم today. See Accuracy notes.

The registry

From IANA's delegation record for .كوم. .كوم is a generic TLD.

Run by: VeriSign SarlBased in Switzerland. Delegated 2015-07-02, record last updated 2026-03-30.
Registry site: www.verisigninc.comWhere the registry documents .كوم — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: tld-rdap.verisign.com · whois.nic.xn--fhbeiWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: ac1.nstld.comac2.nstld.comac3.nstld.comac4.nstld.comThe 4 authoritative servers for the .كوم zone — what the root delegates to. Nothing ds queries 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.

generic IANA Root Zone Database types it "generic"
idn the label is punycode — an internationalised TLD; unicode is how it reads
new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

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 .كوم was delegated to; this is what the root actually answers with when a resolver asks it where .كوم lives.

Delegated to: ac1.nstld.com192.42.173.302001:500:120::30
ac2.nstld.com192.42.174.302001:500:121::30
ac3.nstld.com192.42.175.302001:500:122::30
ac4.nstld.com192.42.176.302001:500:123::30
The 4 name servers the root hands out for .كوم, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC: Signed — 1 DS record in the root
key 14501ECDSA P-256/SHA-256 · SHA-256813D04B5B55EC42C304526218FAA8D38773A1E05BF33B5C728F6ADC6B5290B7F
Each one is a fingerprint of .كوم's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .كوم came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net xn--fhbei. NS and dig +norec @a.root-servers.net xn--fhbei. DS.