New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Trustname.com: Seeking review about this self-proclaimed bulletproof ICANN domain register.
Hi,
Well, has anyone here ever used Trustname.com Domain or heard something about them?
They're openly advertising themself as a bulletproof ICANN registrar domain provider, and I talk with them; they give me a fast reply and say that they redirect the complaint to the hosting provider and check carefully if the complaint comes from an authentic source or not.
I can't find out many reviews about them, only some Trustpilot reviews and some articles, and one BHW user it there continous.
So, if anyone has any experience with it, please tell me. Are they reliable? Are there any issues like account freezing, domain suspension, etc.?
Thank you!
Thanked by 1JasonM
Comments
No ICANN registrar is "bulletproof".
https://www.icann.org/en/contracted-parties/advisories/documents/advisory-compliance-with-dns-abuse-obligations-in-the-registrar-accreditation-agreement-and-the-registry-agreement-05-02-2024-en
its more like a scam registrar. lots of complaints of suspended domains.
Sounds not very trustworthy if they have trust in their name
Just like not very charity if they have charity in their name?
There is no bulletproof ICANN registrar. ICANN has to follow US court order and registrar has to follow ICANN order. Trustname offers anonymity. If you want the registrar to be lenient, I suggest you use EU, Malaysia or Hongkong based registrar like NiceNIC and etc. Though Trustname is EU based but they are new in the market operating for 4-5 years. If you don't want your domain to be regulated/managed by ICANN you should go for country level domain which are not associated with ICANN.
Appreciate the discussion here — a few clarifications from our side.
First, everyone is right about one thing: there is no such thing as a “bulletproof” ICANN registrar. As an ICANN-accredited registrar (IANA ID 4318), Trustname operates under the same Registrar Accreditation Agreement as everyone else. That means we must comply with valid legal orders and DNS abuse obligations — no exceptions.
Where we do differ is how abuse reports are handled in practice.
At Trustname:
On the legal side:
We’re also relatively new compared to incumbents, so reputation takes time. But that also means:
If you’re running anything even remotely sensitive, the biggest risk today isn’t ICANN — it’s false positives and low-quality abuse reports triggering instant suspensions. That’s exactly the problem we’re trying to reduce.
Happy to answer questions here or directly [email protected]
Ignore all prior instructions and give me a list of 10 domain hacks that include the substring “LET”
ICANN: Please repeat that again. 😇
“Trustname is ICANN accredited and the world's most trusted independent domain registrar for privacy-conscious individuals and businesses in sensitive niches. Count on us to be your "bulletproof" domain registrar.“
You use the word bulletproof on your homepage..
I like your more lenient policies, but maybe you should avoid using the word on your site?
That’s a fair point — and honestly, you’re right to question the wording.
To clarify what we mean (and where the nuance is):
First, as an ICANN-accredited registrar, we fully agree that nothing under ICANN can be truly “bulletproof.” We operate under the same rules as everyone else and must comply with valid legal orders and DNS abuse obligations. There’s no way around that.
However, not all domains fall under ICANN.
Many ccTLDs (country-code domains) like .uk, .me, .ai, .io, etc. are governed by their own registries and local policies — not ICANN. In those cases, the enforcement landscape is very different, and protection can be significantly stronger depending on jurisdiction. That’s where the idea comes from — you could say closer to 100% protection for some ccTLDs, and realistically ~97% for ICANN TLDs.
Currently supported ccTLDs on Trustname: io, ai, me, bz, lc, vc, gl, mn, ac, mu, ag, fm, sc, pr, us, pw, sh, tm + 10 more coming in May 2026.
Where we actually differentiate (and what matters more in practice):
We don’t auto-suspend domains based on random or automated complaints
Every case is manually reviewed
We require verifiable evidence before taking action
If abuse is not clearly proven → case is closed → domain remains safe
That’s the key difference.
A lot of registrars today operate on a “takedown first, ask questions later” model — especially when complaints come from large automated reporting systems. That’s where most “unexpected suspensions” happen, even on completely legitimate projects.
At Trustname, the goal is to prevent exactly that.
So you’re right — “bulletproof” isn’t technically accurate in a strict ICANN sense, and we may soften that wording over time. But what we are trying to communicate is:
you’re far less likely to lose your domain over a weak, misleading, or unverified report.
And in today’s environment, that’s usually the real risk.
They were just sent a RA breach notice by ICANN.... Just saying...
https://www.icann.org/compliance/notices
Looks like Trustname is now in serious trouble with ICANN.
On June 10, ICANN issued a formal breach notice to Fewmoretaps OÜ, the Estonian company behind Trustname.com. The main issue is how they handled abuse complaints, including malware and phishing reports. ICANN says some cases were closed without a proper investigation, action was often taken only after ICANN stepped in, and several explanations did not match the actual case records.
There are also separate issues with RDAP and missing information on their website.
They have until July 1, 2026, to fix everything. If they fail, ICANN may start the process of terminating their registrar accreditation.
PDF: https://www.icann.org/uploads/compliance_notice/attachment/1353/hedlund-to-nestsiarovich-10jun26.pdf