.COM.RU

Name: .COM.RU — TLD-Wissensdatenbank
Creator: Coordination Center / RU-Center

Russia

Coordination Center / RU-Center · SubTLD · Aktualisiert 2026-09-10

Open

Technische Daten

Zone: com.ru
Registrierung: Standard (manual processing)
Laufzeit: 1 year
Zeichenlänge: 1-63
Nameserver: 2-7 nameservers
Transfersperre: Ja
Transferdauer: Standard
AuthInfo-Format: N/A
Redemption-Phase: None documented
Handle-Aktualisierung: Ja
Treuhandservice: Ja
WHOIS-Datenschutz: Eingeschränkt
WHOIS-Aktualisierung: Standard
WHOIS-Server: whois.tcinet.ru
Anbindung: Direct
Datensatz: ccTLD

Berechtigung & Einschränkungen

Open to anyone worldwide. No local presence required for standard .ru registration. IDN supported (Cyrillic: .рф). WHOIS must be VERIFIED before auth code can be generated. Sanctions risk: Russia subject to extensive EU, US, and UK sanctions. InterNetX (German registrar) can process .RU operations, but US-connected entities and certain sanctioned Russian entities are restricted.

SANCTIONS COMPLIANCE: Russia subject to EU/US/UK sanctions. Always verify sanctions compliance before processing .RU orders for new customers. Existing portfolio renewals generally permitted but monitor regulatory updates.

WHOIS must be verified before auth code generation. If WHOIS data is inaccurate, auth code request will fail. Update and verify WHOIS first.

Registrierung

1 year. Standard registration. IDN (.рф Cyrillic) available as separate TLD.

Transferverfahren

Manual transfer process. No auth code used by this registry.

📘 ICANN Transfer Policy (IRTP) — See ICANN Transfer Policy for the full IRTP framework, auth code rules, 60-day lock periods, and TEAC.

Inhaberwechsel

Standard process. Deletion of domain previously required postal letter to Moscow (historical). Current process via registrar system.

📘 ICANN OwnerChange (COR) — See ICANN OwnerChange for COR triggers, FOA/DA modes, 60-day lock, and opt-out.

Verlängerung & Löschung

Standard. No RGP documented for some registrar paths. Verify restore availability.

📘 ICANN ERRP — See ICANN ERRP for the standard gTLD expiry lifecycle (Auto-Renew Grace → RGP → Pending Delete → Released).

Wiederherstellung / RGP

No standard RGP documented. Domain may be available for re-registration after deletion. Verify with registry.

No standard RGP. Domain deletion may be irreversible. Always renew before expiry.

📘 ICANN ERRP — See ICANN ERRP for RGP details and standard restore fees.

WHOIS / Datenschutz

WHOIS data must be verified and accurate. Inaccurate WHOIS blocks auth code generation. Standard public WHOIS.

📘 ICANN Registration Data Policy — See Registration Data Policy for RDP 2025, RDAP, redaction defaults, and privacy/proxy rules.

NIS2-Konformität

N/A. Russia not subject to EU NIS2. However, EU sanctions regulations may impose additional compliance requirements on registrars processing .RU domains.

📘 NIS2 Compliance — See NIS2 Compliance for Article 28 requirements, registry implementation status, and operational impact.

Bekannte Fehlercodes & Hinweise

WHOIS verification required: Auth code generation blocked if WHOIS not verified. Must update and verify first.
Sanctions compliance: EU/US/UK sanctions apply. Check before processing. InterNetX (German) can process but US-connected entities restricted.
No standard RGP: No documented RGP. Deletion may be permanent. Renew before expiry.
Zero friction today: Currently 0.00 friction (100% VIP, zero tickets). Any sanctions policy change would immediately hit VIP queue.
IDN .рф: Cyrillic IDN available as separate TLD registration, not variant of .RU.

Verantwortliche für Registrierungsdaten

Coordination Center for TLD RU (org) 8 Marta street 1, bld 12, Moscow 127083, Russian Federation (the)
Coordination Center for TLD RU — .RU domain Administrative group (admin) 8 Marta street 1, bld 12, Moscow 127083, Russian Federation (the)

Fehlercodes

EF01017
EF03018
EF03017
EF01075
EF03011
EF03058
EF01055
EF03010
EF01074
EF02080
EF0103118
EF03009
EF03008
EF00512
EF01008
EF01009
EF03005
EF01002
EF03007
EF03006
EF02077
EF02076
EF01022
EF03040
EF02074

Pflichtfelder

techc/email
ownerc/email
adminc/email

Einschränkungen

Eine Aufhebung der Löschung (Restore) ist nur beim Ablaufen der Registrierungsperiode möglich. Bei explizit gelöschten Domains ist eine Aufhebung nicht möglich.
Nameserver müssen vorher eingerichtet sein und autoritativ antworten.
Domains können ohne weitere Einschränkungen registriert werden.
HR-Nummer (Firmen) oder Personalausweis-Nummer (Privatperson) erforderlich.

Root-Nameserver

F.DNS.RIPN.NET
A.DNS.RIPN.NET
D.DNS.RIPN.NET
B.DNS.RIPN.NET
E.DNS.RIPN.NET

Aufträge (API)

create · verfügbar · kostenpflichtig · automatisch
update · verfügbar · kostenpflichtig · manuell
transfer · verfügbar · kostenpflichtig · manuell
preack · verfügbar · manuell
delete · verfügbar · manuell