ds

.post

Generic top-level domain

RDAP + WHOISsold by 1 registrarBusiness & Work

Register
$274.99first year
Renew
$274.99a year
Transfer
$274.99to move it
Registrars
1quoting it
Lookup
RDAP + WHOISanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.post

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 post

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

Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .post is the mean of the registration column — $274.99, which undercuts 6% of the 881 priced TLDs.

RegistrarRegisterRenewTransfer
101domain.com$274.99$274.99$274.99
Mean — what ds prints$274.99$274.99$274.99

List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.

Where to register

One registrar in the bundled table publishes a registration price for .post, which is evidence it sells it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld post --where prints them.

Put a name in the box above and each link becomes that registrar's search for mybrand.post, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.

Who can register

No eligibility rule is on file for .post, 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. .post has both, so RDAP answers and WHOIS is the fallback if it does not.

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.post — a 404 means the name is free.
WHOIS
whois.nic.postQueried on port 43, from the bundled whois.json. The name is called free when the reply contains domain not found — text matching, which is why RDAP is preferred where it exists.

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

The registry

From IANA's delegation record for .post. .post is a sponsored TLD.

Run by
Universal Postal UnionBased in Switzerland. Delegated 2012-08-07, record last updated 2025-05-15.
Registry site
www.upu.intWhere the registry documents .post — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.identitydigital.services · whois.nic.postWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
v0n0.nic.postv0n1.nic.postv0n2.nic.postv0n3.nic.postv2n0.nic.postv2n1.nic.postThe 6 authoritative servers for the .post 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.

  • sponsored IANA Root Zone Database types it "sponsored"
  • legacy-gtld ICANN delegated it before 2013-10-23 — 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.

  • Business & Work Companies, corporate forms, trade, and finding work.

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

Delegated to
  • v0n0.nic.post65.22.0.12a01:8840::1
  • v0n1.nic.post65.22.1.12a01:8840:1::1
  • v0n2.nic.post65.22.2.12a01:8840:2::1
  • v0n3.nic.post65.22.3.12a01:8840:3::1
  • v2n0.nic.post65.22.4.12a01:8840:4::1
  • v2n1.nic.post65.22.5.12a01:8840:5::1
The 6 name servers the root hands out for .post, 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 35725RSA/SHA-256 · SHA-2565B8265DC3F1952980AB5369253C4A4ED9D674D91B8C39360B22A7DEAEF168FE0
Each one is a fingerprint of .post'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 .post 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 post. NS and dig +norec @a.root-servers.net post. DS.

Also answered by rdap.identitydigital.services

and 438 more zones on the same server.

Priced near it