ds

.org.in

Country-code top-level domain for India — names are registered at the third level, under .in

WHOISsold by 1 registrar

Register
$5.80first year
Renew
$5.80a year
Transfer
$5.80to move it
Registrars
1quoting it
Lookup
WHOISanswers for it
DNSSEC
Signed1 DS record in the root
Level
Thirdmybrand.org.in

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 org.in

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 .org.in is the mean of the registration column — $5.80, which undercuts 99% of the 881 priced TLDs.

RegistrarRegisterRenewTransfer
porkbun.com$5.80$5.80$5.80
Mean — what ds prints$5.80$5.80$5.80

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 .org.in, which is evidence it sells it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld org.in --where prints them.

Put a name in the box above and each link becomes that registrar's search for mybrand.org.in, 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 .org.in, 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. .org.in has no RDAP service, so the answer comes from WHOIS text on port 43.

WHOIS
whois.registry.inQueried on port 43, from the bundled whois.json. The name is called free when the reply contains No Data Found — text matching, which is why RDAP is preferred where it exists.

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

The registry

From IANA's delegation record for .in — .org.in is a zone under it, so the registry, the servers and the dates below are .in's. .org.in is a country-code TLD.

Run by
National Internet Exchange of IndiaBased in India. Delegated 1989-05-08, record last updated 2026-06-29.
Registry site
registry.inWhere the registry documents .in — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nixiregistry.in · whois.nixiregistry.inWhat the registry itself tells IANA it runs. Note: the bundled table asks whois.registry.in instead — one of them is out of date, and ds falls back to asking IANA when a bundled host goes stale.
Name servers
ns1.registry.inns2.registry.inns3.registry.inns4.registry.inThe 4 authoritative servers for the .in 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 .in was delegated to; this is what the root actually answers with when a resolver asks it where .in lives. .org.in is not in the root zone — nothing below the top level is. It resolves because .in does, on .in's servers.

Delegated to
  • ns1.registry.in64.96.1.12620:57:4001::1
  • ns2.registry.in64.96.2.12620:57:4002::1
  • ns3.registry.in64.78.204.12620:171:812:1534:8::1
  • ns4.registry.in64.78.205.12620:171:813:1534:8::1
The 4 name servers the root hands out for .in, 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 10094ECDSA P-256/SHA-256 · SHA-2565824EE9A55ED72F0D46D2C3A511F393F05EFC27E73CBD1005BEBBC73402B6186
Each one is a fingerprint of .in'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 .org.in 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 in. NS and dig +norec @a.root-servers.net in. DS.

Under .in

Priced near it