.ru WHOIS Lookup
.ru is the country-code extension of Russia, administered by the Coordination Center. Look up a .ru address and see what the record contains.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.ru WHOIS Lookup: Record Fields and Date Lines
.ru is the country code extension of the Russian Federation, delegated into the root zone on 7 April 1994 and administered by the Coordination Center for TLD RU. Queries are answered on port 43 by whois.tcinet.ru. In our measurement on 12 August 2026 the reply carried twelve fields with lower-case labels. The zone holds a DS record in the root, so it is signed with DNSSEC.
The date side is what sets this extension apart. The reply gives the creation date in created, the end of the paid term in paid-till and the day the name returns to registration in free-date. Across the three records we measured, roughly a month separated the last two — so it can be read directly that a name does not become free the moment its term ends, and that a waiting window sits in between.
Status is not a single word but a comma-separated list: in the records we measured the name was marked as registered, delegated to the zone and verified as to its holder. Fields set aside for the holder — an organisation line and a taxpayer identifier — are present in the reply, yet all three records we measured returned them empty. The admin contact arrives as a web address rather than an email. To compare neighbouring markets, see the .kz WHOIS lookup and .tr WHOIS lookup pages.
About the .ru extension
- Extension
- .ru
- WHOIS server
- whois.tcinet.ru
- RDAP endpoint
- This extension has no RDAP endpoint in the IANA bootstrap registry.
- Registry
- Coordination Center for TLD RU
- Delegated
- 7 April 1994
- Fields measured
- 12 fields (12 August 2026)
- Three dates
- created, paid-till and free-date are published separately
- RDAP
- IANA's bootstrap registry defines no endpoint for .ru
WHOIS FAQ
What does the free-date field mean in a .ru record?
It gives the day the name returns to registration. The paid term ends on the paid-till date, but the name is not released then: the holder keeps a recovery right for a while longer, and free-date marks the end of that period. In the three records we measured, roughly a month separated the two dates. If you are watching a name, the second date is the one to wait for, not the first.
Does a .ru WHOIS lookup show the holder of the domain?
In the records we measured it did not. The reply carries an organisation line and a taxpayer identifier line set aside for the holder, yet all three records returned both empty. When the organisation line is filled it names a legal entity; for records held by natural persons, identity data is not opened on this channel. For contact, the reply points to a web address at the registrar rather than an email.
Why does the state line in a .ru record carry several values?
Because the registry does not compress status into one word; it gives a comma-separated list. In the records we measured three values arrived together: that the name is registered, that it is delegated into the zone, and that its holder has been verified. Those answer three different questions — is there a registration, does the name resolve, has the holder been checked. They have no one-to-one equivalent among EPP codes.
What are the addresses beside .ru name server lines?
The registry lists name servers not by host name alone but with their IPv4 and IPv6 addresses; in the record we measured each server line carried both. That shows at a glance that the server is reachable over either protocol and removes a separate resolution step. Replies from generic extensions do not carry those addresses at all — only the host name appears.
Can the creation date and age of a .ru domain be read?
They can. The created field gives the registration date to the second in UTC; of the records we measured one dated from 1997 and another from 2006. Our result screen derives the domain's age from that date and separately shows the days remaining on the paid term. The reply carries no separate update date, so when the record was last edited cannot be learned on this channel.
Can .ru registration data be queried over RDAP?
No. IANA's RDAP bootstrap registry defines no endpoint for .ru, which our measurement confirmed. Since 28 January 2025 RDAP has been the definitive source of registration data for generic extensions, but country code extensions sit outside that arrangement and each registry decides for itself. So the port 43 WHOIS service is the only machine-readable source for .ru data.
Why is the admin contact a link in a .ru record?
Because the registry writes the address of the registrar's own lookup page into that field instead of an email address. All three records we measured used the same form. The meaning is this: a contact request is routed into the registrar's own channel rather than straight to a mailbox. It is the registry's way of keeping a route to the holder open without opening personal data.
How does an available .ru name appear in a lookup?
Query a name nobody holds and the server reports that no match was found, with none of the twelve fields present. That means the name looks free to register. We keep such a result for five minutes only and registered ones for six hours, the short window being there because a name that looks free can be taken quickly.