ds

.рус.xn--p1acf

Internationalised top-level domain

RDAPPlaces

Register
—first year
Renew
—a year
Transfer
—to move it
Registrars
—quoting it
Lookup
RDAPanswers for it
DNSSEC
Signed2 DS records in the root
Level
Secondmybrand.рус

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 xn--p1acf

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 .рус, 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 .рус, 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. .рус has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP
https://rdap.nic.xn--p1acfFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nic.xn--p1acf/domain/mybrand.xn--p1acf — a 404 means the name is free.

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

The registry

From IANA's delegation record for .рус. .рус is a generic TLD.

Run by
Rusnames LimitedBased in Russian Federation. Delegated 2014-07-03, record last updated 2025-12-04.
Registry site
rusnames.ruWhere the registry documents .рус — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nic.xn--p1acfWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
ns1.anycastdns.czThe 1 authoritative server for the .рус 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.

  • generic IANA Root Zone Database types it "generic"
  • idn the label is punycode — an internationalised TLD; unicode is how it reads
  • new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — 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.

  • Places Cities, regions, and parts of the world.

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

Delegated to
  • ns1.nic.xn--p1acf72.42.113.22620:171:d01:dc::2
  • ns1.anycastdns.cz185.38.108.1082a00:fea0:dead::beef
  • ns2.nic.xn--p1acf72.0.49.22620:171:a01:ad::2
The 3 name servers the root hands out for .рус, 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 — 2 DS records in the root
  • key 11446RSA/SHA-256 · SHA-256C39B9FB91B155CA7FF3F84BC7F7B7713E8D3B40AE9B7B0D9C3DE0FDC36FA325C
  • key 50380RSA/SHA-256 · SHA-256575AC79F934055ECFFB95E4485C9BF8EABD39F7AB379C14566A1550081343BE6
Each one is a fingerprint of .рус'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 .рус came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

The record and the zone disagree. The root zone answers with ns1.nic.xn--p1acf, ns2.nic.xn--p1acf, which the record does not name. The zone is what resolvers use, so it is the one that counts; the record is maintained by hand and lags a change of servers.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net xn--p1acf. NS and dig +norec @a.root-servers.net xn--p1acf. DS.