ICANN sends breach notice to TrustName
A registrar that advertises tolerance for sensitive niches just learned that ICANN's abuse rules do not make exceptions.
ICANN sent a breach notice to Fewmoretaps OU, operating as TrustName.com. The stated cause is not billing or renewal mechanics; it is DNS abuse handling.
TrustName has built its business around 'sensitive niches,' which tend to generate a steady flow of abuse complaints. The breach notice says the registrar has not been dealing with them as its contract requires.
This is the enforcement machinery working as designed. A breach notice is formal escalation, not a suggestion: ICANN is telling the registrar to clean up its abuse response inside a set window or face consequences.
The marketing language about sensitive niches is irrelevant to the contract. Registrars can choose their clientele, but they cannot choose which contractual obligations follow.
For anyone holding domains at a registrar under enforcement, the practical risk is real: suspensions, transfer holds, or forced registrar changes can ripple downstream. Registrar stability is part of an asset's value.
The clock is now running on TrustName. How it responds will determine whether this stays a corrective notice or becomes something worse.
We hope our commentary provided you value, please don't forget to also read the source article at Domain Name Wire.