Registrar that catered to registrants likely to receive DNS abuse complaints loses its accreditation
ICANN has terminated the accreditation of Fewmoretaps OU, which operated under the name TrustName.com. The decision follows a series of breach notices from ICANN related to the registrar’s handling of DNS abuse complaints and its obligations under ICANN policy.
TrustName built its brand around privacy and protection for clients in sensitive or high-risk industries. On its site, the company described itself as a registrar for “privacy-conscious individuals and businesses in sensitive niches,” and at one point promoted itself as a “bulletproof” domain registrar. More recently, the registrar characterized its offering as “built for businesses in competitive niches that often face false or bad-faith abuse reports.” Those statements indicate the registrar aimed to attract customers who frequently encounter abuse reports.
ICANN’s notices to the registrar criticized how those abuse complaints were being addressed. While the specific contents of the notices are part of ICANN’s compliance process, the public outcome is clear: the accreditation has been terminated. When ICANN concludes that a registrar has not met its contractual or policy obligations, termination of accreditation is one of the enforcement tools available to protect the integrity of the domain name system and ensure registrant data and abuse-handling standards are met.
The size of the registrar appears to have been modest. Despite marketing claims that it was “Trusted by millions of domain owners,” the most recent Verisign registry reports show that TrustName had roughly 4,000 .com domains under management. That figure provides a snapshot of the registrar’s footprint in one major top-level domain, though it does not enumerate registrations in other extensions.
Termination of a registrar’s accreditation can have several practical consequences for registrants and for the broader DNS ecosystem. Registrants typically need clear direction about the transfer or renewal of their domains, the preservation of registration data, and how ongoing abuse complaints will be handled. ICANN and registries usually put transition mechanisms in place to minimize disruption, and affected registrants are often notified about options to transfer to other accredited registrars.
For domain industry observers, the case highlights ongoing tensions between registrars that market themselves as protective or privacy-focused and the expectations placed on accredited registrars to respond promptly and effectively to abuse reports. ICANN’s registrar accreditation agreement and related policies require accredited registrars to have processes that address DNS abuse, respond to reports, and cooperate with relevant parties when legitimate abuse occurs. Where a registrar appears to be operating in a way that undermines those requirements, ICANN’s compliance program can initiate notices, corrective action requirements, and—if necessary—termination.
The TrustName situation also demonstrates the importance of careful scrutiny of marketing language. Terms like “bulletproof” and prominent emphasis on privacy and protection can attract registrants who seek to evade abuse mitigation, which in turn draws regulatory and contractual scrutiny. Registrars must balance protecting legitimate privacy and free expression needs with responsibilities to prevent and remediate abuse that harms users and infrastructure.
At this time, ICANN’s termination stands as the recorded enforcement outcome. Affected registrants and interested parties should monitor official ICANN communications and registry notifications for guidance on transfers, renewals, and any compliance-related timelines. The broader domain community will likely continue to watch how ICANN applies its compliance framework to similar cases going forward.