.su
Country-code top-level domain for the former Soviet Union
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- WHOISanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.su
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld suAdd --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 .su, 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 .su, 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. .su has no RDAP service, so the answer comes from WHOIS text on port 43.
- WHOIS
whois.ripn.netQueried on port 43, from the bundled whois.json. The name is called free when the reply containsNo entries found— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld su --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .su today. See Accuracy notes.
The registry
From IANA's delegation record for .su. .su is a country-code TLD.
- Run by
- Russian Institute for Development of Public Networks (ROSNIIROS)Based in Russian Federation. Delegated 1990-09-19, record last updated 2026-08-05.
- Published services
whois.tcinet.ruWhat the registry itself tells IANA it runs. Note: the bundled table askswhois.ripn.netinstead — one of them is out of date, anddsfalls back to asking IANA when a bundled host goes stale.- Name servers
a.dns.ripn.netb.dns.ripn.netc.tld-servers.rud.dns.ripn.nete.dns.ripn.netf.dns.ripn.netThe 6 authoritative servers for the .su zone — what the root delegates to. Nothingdsqueries 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-codeIANA 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 .su was delegated to; this is what the root actually answers with when a resolver asks it where .su lives.
- Delegated to
a.dns.ripn.net193.232.128.62001:678:17:0:193:232:128:6b.dns.ripn.net194.85.252.622001:678:16:0:194:85:252:62c.tld-servers.ru194.190.122.172a09:bd00:1:0:194:190:122:17d.dns.ripn.net194.190.124.172001:678:18:0:194:190:124:17e.dns.ripn.net193.232.142.172001:678:15:0:193:232:142:17f.dns.ripn.net193.232.156.172001:678:14:0:193:232:156:17
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 42982RSA/SHA-256 · SHA-256
7B533AF433CC945BF785F3C500A279B052DFD76658E484C70CCE40C2A9FBC251
- key 42982RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net su. NS and dig +norec @a.root-servers.net su. DS.