.ye

Country-code top-level domain for Yemen

RDAP + WHOIS

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: RDAP + WHOISanswers for it
DNSSEC: Unsignedno DS in the root
Level: Secondmybrand.ye

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 ye

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

RDAP: https://rdap.y.net.yeFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.y.net.ye/domain/mybrand.ye — a 404 means the name is free.
WHOIS: whois.y.net.yeQueried on port 43, from the bundled whois.json. The name is called free when the reply contains not found — text matching, which is why RDAP is preferred where it exists.

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

The registry

From IANA's delegation record for .ye. .ye is a country-code TLD.

Run by: TeleYemenBased in Yemen. Delegated 1996-08-19, record last updated 2025-03-16.
Published services: rdap.y.net.ye · whois.y.net.yeWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: d.tld.yee.tld.yetld1.yetld2.yetld3.yeThe 5 authoritative servers for the .ye 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.

country-code IANA Root Zone Database types it "country-code"

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

Delegated to: d.tld.ye204.61.216.1532001:500:14:6153:ad::1
e.tld.ye185.119.138.102a01:5b0:9::a
tld1.ye195.94.10.222a02:e280:8:1000::1
tld2.ye195.94.13.222a02:e280:8:2000::1
tld3.ye82.114.164.2442a02:2718:8:d3::244
The 5 name servers the root hands out for .ye, 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: UnsignedThe root publishes no DS record for .ye, so the chain of signatures stops at the root and a resolver has no way to prove an answer under .ye is genuine — it takes it on trust, as all of the DNS did before DNSSEC. 88 of the 1,438 TLDs in the root are in the same position. Names here still work; they are just not verifiable.

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