Who operates RUTrustee?

Verify the operator

Atak Domain Bilgi Teknolojileri A.Ş. is listed by ICANN under IANA 1601. Go and look. That accreditation concerns gTLD registrar activity, while .RU procedures follow Russian domain rules and the current registrar’s process, which is a separate question and worth keeping separate.

For company-wide context, Atak Domain reports 100K+ active customers in 200+ countries, 23+ years in domain and hosting, and 1,600+ supported TLDs. Read those as figures for Atak Domain as a whole, not for the .RU service described on this site.

The company’s own .RU service steps are set out in Atak Domain’s published guide ↗.

The operator on the record

Everything below is checkable from outside this site. The registrar ID ties the company to a public IANA assignment, and its RDAP service answers registration queries directly.

• ICANN accredited registrar list, filtered to IANA 1601 icann.org
• IANA registrar ID assignments iana.org
• The registrar’s RDAP service rdap.atakdomain.com

Full postal and department contacts sit on Atak Domain’s contact page ↗.

What we check

For a domain that already exists, four facts come first: its registrar, the administrator of record, its status and its expiry date. Those facts decide the rest. They show whether direct ESIA verification is realistic, whether an accepted document route is open, or whether a formal change to an eligible trustee belongs on the table at all.

How we document guidance

Regulatory explanations link to Coordination Center material ↗. Service prices and application steps link to Atak Domain, because that is where they are quoted and processed. Where a route depends on a registrar’s current process rather than on a published rule, the page says so. Nobody here promises approval, and nobody here promises uninterrupted renewal.

Contact and escalation

Request a case review through the contact page. Include the domain, and the existing ticket reference if you have one. One thing people get wrong on the first message: identity scans follow a separate document process, so keep them out of an initial e-mail. Send the domain first, and the paperwork when support asks for it.