ds

.msk.ru

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

WHOIS

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
Thirdmybrand.msk.ru

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 msk.ru

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 .msk.ru, 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 .msk.ru, 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. .msk.ru has no RDAP service, so the answer comes from WHOIS text on port 43.

WHOIS
whois.relcom.ruQueried on port 43, from the bundled whois.json. The name is called free when the reply contains No entries found — text matching, which is why RDAP is preferred where it exists.

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

The registry

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

Run by
Coordination Center for TLD RUBased in Russian Federation. Delegated 1994-04-07, record last updated 2026-08-21.
Registry site
www.cctld.ruWhere the registry documents .ru — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
whois.tcinet.ruWhat the registry itself tells IANA it runs. Note: the bundled table asks whois.relcom.ru instead — one of them is out of date, and ds falls 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 .ru 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 .ru was delegated to; this is what the root actually answers with when a resolver asks it where .ru lives. .msk.ru is not in the root zone — nothing below the top level is. It resolves because .ru does, on .ru's servers.

Delegated to
  • a.dns.ripn.net193.232.128.62001:678:17:0:193:232:128:6
  • b.dns.ripn.net194.85.252.622001:678:16:0:194:85:252:62
  • c.tld-servers.ru194.190.122.172a09:bd00:1:0:194:190:122:17
  • d.dns.ripn.net194.190.124.172001:678:18:0:194:190:124:17
  • e.dns.ripn.net193.232.142.172001:678:15:0:193:232:142:17
  • f.dns.ripn.net193.232.156.172001:678:14:0:193:232:156:17
The 6 name servers the root hands out for .ru, 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 26734RSA/SHA-256 · SHA-256C48BE23D7998AFA2EF0993609413E58BC7EE9E356642A7182F2C3EA321FA9911
Each one is a fingerprint of .ru'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 .msk.ru 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 ru. NS and dig +norec @a.root-servers.net ru. DS.

Under .ru