.safety

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

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 safety

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

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

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

The registry

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

Run by: Jolly Host, LLCBased in United States of America. Delegated 2015-04-23, record last updated 2026-07-08.
Registry site: www.identity.digitalWhere the registry documents .safety — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: rdap.identitydigital.servicesWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: v0n0.nic.safetyv0n1.nic.safetyv0n2.nic.safetyv0n3.nic.safetyv2n0.nic.safetyv2n1.nic.safetyThe 6 authoritative servers for the .safety 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

What it is for

Our reading, not a fact — nothing in the root zone says what a TLD means. Hand-maintained in tld-categories.json.

Internet & Technology Software, hosting, data, devices, and the web itself.

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

Delegated to: v0n0.nic.safety65.22.36.412a01:8840:26::41
v0n1.nic.safety65.22.37.412a01:8840:27::41
v0n2.nic.safety65.22.38.412a01:8840:28::41
v0n3.nic.safety161.232.18.412a01:8840:10e::41
v2n0.nic.safety65.22.39.412a01:8840:29::41
v2n1.nic.safety161.232.19.412a01:8840:10f::41
The 6 name servers the root hands out for .safety, 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 6139RSA/SHA-256 · SHA-25601E166CB1C6A2797FBDEFFBE26B009A7A1F72905F476353537DFA63754B479DE
Each one is a fingerprint of .safety'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 .safety 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 safety. NS and dig +norec @a.root-servers.net safety. DS.