ds

.able

Generic top-level domain

RDAP

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.able

Check a name

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

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 able

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 .able, 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 .able, 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. .able has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP
https://rdap.nic.ableFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nic.able/domain/mybrand.able — a 404 means the name is free.

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

The registry

From IANA's delegation record for .able. .able is a generic TLD.

Run by
Able Inc.Based in Japan. Delegated 2016-03-03, record last updated 2024-05-11.
Registry site
www.able.co.jpWhere the registry documents .able — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nic.ableWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
a.nic.ableb.nic.ablec.nic.ablens1.dns.nic.ablens2.dns.nic.ablens3.dns.nic.ableThe 6 authoritative servers for the .able 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"
  • 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 .able was delegated to; this is what the root actually answers with when a resolver asks it where .able lives.

Delegated to
  • a.nic.able37.209.192.102001:dcd:1::10
  • b.nic.able37.209.194.102001:dcd:2::10
  • c.nic.able37.209.196.102001:dcd:3::10
  • ns1.dns.nic.able156.154.144.32610:a1:1071::3
  • ns2.dns.nic.able156.154.145.32610:a1:1072::3
  • ns3.dns.nic.able156.154.159.32610:a1:1073::3
The 6 name servers the root hands out for .able, 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 48877RSA/SHA-256 · SHA-2566EFFEC2F6DB34B2D1086A3B4CEDD6E4109135877E533D6D1BF0F7CA760EB018F
Each one is a fingerprint of .able'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 .able 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 able. NS and dig +norec @a.root-servers.net able. DS.