ds

.int

Generic top-level domain

RDAPrestrictedGovernment & Politics

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

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 int

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 .int, 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

intergovernmental organisations established by treaty only.

Availability and eligibility are different questions, and ds answers the first: a name here reported AVAILABLE means the label is free, not that this registry will sell it to you. The note is hand-maintained and was last checked on 2026-09-02; the registry page it links to, not this one, is the authority. All 81 restricted TLDs, under 27 rules, are listed on Who can register.

How ds answers for it

RDAP first, WHOIS second — the same order for every TLD. .int has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

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

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

The registry

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

Run by
Internet Assigned Numbers AuthorityBased in United States of America. Delegated 1988-11-03, record last updated 2026-03-10.
Registry site
www.iana.orgWhere the registry documents .int — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.iana.org · whois.iana.orgWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
ns.uu.netns0.ja.netsec2.authdns.ripe.netx.iana-servers.nety.iana-servers.netz.iana-servers.netThe 6 authoritative servers for the .int 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"

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.

  • Government & Politics The public sector, the armed forces, and elections.

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

Delegated to
  • x.iana-servers.net199.43.135.532001:500:8f::53
  • y.iana-servers.net199.43.133.532001:500:8d::53
  • z.iana-servers.net199.43.134.532001:500:8e::53
  • ns.uu.net137.39.1.3
  • ns0.ja.net128.86.1.20193.63.94.202001:630:0:8::142001:630:0:9::14
  • sec2.authdns.ripe.net193.0.9.42a13:27c0:30::4
The 6 name servers the root hands out for .int, with the glue addresses that come with them — 5 of them answer 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 59895ECDSA P-256/SHA-256 · SHA-25610C789F286599316D3A74C2C513434C3F8A33B9238976D5DE2A178E54DA353F3
Each one is a fingerprint of .int'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 .int 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 int. NS and dig +norec @a.root-servers.net int. DS.