TrustName Customers Report Stolen Domains After ICANN Termination Notice

Several TrustName customers say domains were pushed out of their accounts and transferred away without permission, with some reporting that two-factor authentication was enabled. The claims surfaced after ICANN terminated the accreditation of Fewmoretaps OU d/b/a Trustname.com, effective 11 September 2026.

By Hasnaat Mahmood Published Updated
Ech, the Find Cheap Domains mascot

Ech’s short answer

Several customers are alleging unauthorised domain transfers, but the theft claims remain allegations

Domain Name Wire reported on 1 September that multiple TrustName customers say domains were moved out of their accounts without permission. At least one customer said a domain was pushed to another TrustName account and later transferred to Dynadot despite repeated requests for a transfer lock. ICANN’s decision to terminate TrustName’s accreditation was separate and was based on unresolved DNS-abuse compliance failures.

  • Customers report transfers despite 2FA
  • ICANN termination takes effect 11 September
  • The termination was for DNS-abuse compliance failures

TrustName is facing a new problem just days after receiving an ICANN termination notice: several customers are now alleging that domains were removed from their accounts without authorisation and, in some cases, transferred to other registrars.

The reports are serious, but they need to be described carefully. ICANN did not terminate TrustName because of these alleged domain thefts. Its 27 August notice concerned repeated failures to investigate and mitigate DNS abuse. The customer transfer allegations emerged around the same period and are a separate issue that is still being disputed.

Part 01

TrustName customers say domains were pushed out of their accounts without permission

Domain Name Wire says multiple customers have reported similar incidents, including accounts where two-factor authentication was enabled.

Domain Name Wire reported on 1 September that several TrustName customers claim domains were moved from their accounts after ICANN’s termination notice. The report describes domains first being pushed internally to another TrustName account before some were transferred to outside registrars.

One customer, Ijon Tichy, told the publication that his domain was pushed to another TrustName account on 28 August. He said he contacted the registrar several times and asked for a transfer lock to be applied, but the domain was subsequently transferred to Dynadot on 30 August.

Tichy also said two-factor authentication had been enabled on his TrustName account. Other customers quoted or referenced in the report made similar claims about 2FA and unauthorised account activity.

TrustName and the customer disagree over the login evidence

According to Domain Name Wire, TrustName pointed to logins associated with different apparent locations and said it could not conclude that the transfer was unauthorised. Tichy argued that the IP addresses were commercial VPN exit nodes and did not demonstrate genuinely separate physical locations. That disagreement has not been independently resolved.

There is no public finding that TrustName itself stole customer domains

Customers are alleging domain theft and unauthorised transfers, but the public evidence currently consists of customer reports, registrar communications and transfer records described by third parties. It would be premature to state that TrustName, an employee or any specific person was responsible for the alleged thefts without a completed investigation or formal finding.

Part 02

ICANN terminated TrustName over unresolved DNS-abuse compliance failures

The termination notice was issued on 27 August and becomes effective on 11 September 2026.

TrustName is the trading name of Fewmoretaps OU, an Estonia-based registrar with IANA registrar ID 4318. ICANN’s 27 August notice says the company’s Registrar Accreditation Agreement is terminated under sections 5.5.4 and 5.5.6 of the agreement, with the termination becoming effective 11 September 2026.

ICANN said breach notices issued on 10 June and 26 June had not been fully cured. The remaining violations included failures to take prompt and appropriate action to stop or disrupt registered domains being used for DNS abuse, and failures to reasonably and promptly investigate and respond to abuse reports.

The termination notice also says TrustName received four notices of fundamental and material breach over a 78-day period: 10 June, 26 June, 16 July and 26 August 2026. ICANN said repeated remediation measures had not demonstrated effective compliance.

  • 10 June

    ICANN issued an initial formal breach notice focused heavily on TrustName’s handling of DNS-abuse reports.

  • 26 June

    A further breach notice addressed additional abuse-handling cases and unresolved compliance issues.

  • 16 July and 26 August

    Further breach notices meant ICANN counted four fundamental and material breaches within 78 days.

  • 27 August

    ICANN issued the termination notice, with the accreditation scheduled to end on 11 September.

  • The alleged domain thefts were not the reason ICANN terminated the registrar

    ICANN’s termination letter is about DNS-abuse handling and repeated contractual breaches. The customer allegations about unauthorised transfers surfaced after the termination notice and should be treated as a separate developing story.

    Part 03

    ICANN says TrustName domains will be transitioned to another accredited registrar

    De-accreditation does not mean legitimately registered domains simply disappear, but disputed transfers may need to be handled separately.

    ICANN’s termination letter says it will use its De-Accredited Registrar Transition Procedure to move domain names currently managed by TrustName to a qualified ICANN-accredited registrar. ICANN’s general guidance also states that names sponsored by a terminated registrar must be transferred to an accredited registrar.

    That transition process is important for customers whose domains remain properly inside their TrustName accounts. It is a different issue from a domain that was allegedly transferred out to another registrar before the de-accreditation takes effect. A bulk transition of TrustName’s remaining portfolio would not necessarily reverse a disputed transfer that has already completed elsewhere.

    At the time of writing, ICANN’s public bulk-transfer page did not yet list TrustName or Fewmoretaps OU. ICANN notes that bulk transfers caused by an accreditation termination take place after the termination date, so customers should watch for the gaining registrar to be announced as the 11 September date approaches and passes.

    • Domains still at TrustName should be covered by ICANN’s de-accredited registrar transition process
    • A completed disputed transfer to another registrar may require a separate unauthorised-transfer complaint
    • The gaining registrar for TrustName’s remaining portfolio had not been publicly listed at the time of writing
    • Keep registration, billing and ownership records ready in case the new registrar asks customers to verify details
    ICANN cannot simply order a domain returned to a registrant in every unauthorised-transfer case

    ICANN’s guidance says affected registrants should contact the registrar immediately and may submit an Unauthorized Transfer Complaint. In some cases, a registrar can initiate a dispute under the Transfer Dispute Resolution Policy. That process is distinct from the normal de-accredited registrar transition.

    Part 04

    TrustName customers should verify every domain and preserve evidence now

    Owners do not need to assume their domains are affected, but the combination of the customer reports and the pending de-accreditation makes an immediate account check sensible.

    1. Check every domain’s current registrar Use RDAP or ICANN Lookup and compare the result with the domains you expect to see in your TrustName account.
    2. Save evidence before anything changes Keep screenshots, transfer emails, ticket numbers, invoices, account alerts and any available login or 2FA records.
    3. Ask for a lock on disputed domains Contact TrustName and, if a domain has already moved, the gaining registrar. Explain that the transfer is disputed and request that further movement is prevented while it is investigated.
    4. Secure the connected email account Change passwords where appropriate, review active sessions and make sure the email account controlling domain recovery is protected with strong 2FA.
    5. File an ICANN complaint where applicable ICANN provides an Unauthorized Transfer Complaint route for registrants who believe a domain was transferred or registration data changed without permission.
    6. Watch the TrustName transition Customers with unaffected domains should monitor ICANN for the gaining registrar and instructions once the de-accreditation becomes effective.

    If a domain has already moved to another registrar

    Act quickly and keep the communication factual. Give both registrars the domain name, the transfer date, your account evidence and the reason you believe the transfer was unauthorised. Ask for written case numbers and preserve every reply. If the gaining registrar locks the domain during an investigation, that can at least reduce the risk of another rapid transfer while the dispute is reviewed.

    ICANN specifically advises registrants who believe a domain was transferred without permission to contact the registrar immediately and submit an Unauthorized Transfer Complaint. It also notes that a registrar may in some circumstances initiate a dispute under the Transfer Dispute Resolution Policy.

    Ech, the Find Cheap Domains mascot

    Bottom line

    TrustName’s final days as an ICANN-accredited registrar now have a second major issue to watch

    ICANN has already decided to terminate TrustName’s accreditation over repeated DNS-abuse compliance failures, effective 11 September. Separately, customers are now reporting domains being pushed out of accounts and transferred without their permission. Those theft claims are not yet a formal finding, but affected owners should verify their domains, preserve evidence and use the registrar and ICANN complaint routes immediately if anything has moved unexpectedly.

    Leave a Reply

    Hasnaat Mahmood

    Written by

    Hasnaat Mahmood

    Hasnaat is the founder of Find Cheap Domains and personally manages a portfolio of more than 300 domains. His experience covers domain selection, registrations, renewals, transfers, DNS management and long-term ownership costs.

    Domain portfolio owner · 300+ domains managed