Who runs TLDBunker, and how to check our work

TLDBunker is a privacy-first VPS host: you order with a 32-character random ID, pay in Monero or Bitcoin, and run your own infrastructure without ever handing us a name, an email or an identity document. Selling that kind of anonymity puts a specific obligation on us — we have to be unusually clear about who we are, and about where your server physically lives.

TLDBunker is not incorporated yet, so this site is published by the TLDBunker team. The incorporated entity and its jurisdiction will be named here before ordering opens, and we would rather show you that as an honest gap than paper over it with a vague phrase like “an offshore company.” It resolves to a real registered company and a named jurisdiction before launch, as part of the legal review that gates this whole project. The same disclosure appears on every site in our network, so the editor behind the pages is never a mystery.

We are a privacy host, not a “bulletproof” one. We publish an Acceptable Use Policy, we run a real abuse desk, and we answer legitimate legal process without ever exposing customer data beyond what the law actually compels. Knowing which law that is — which country, which court — is exactly why the entity and jurisdiction cannot stay fuzzy.

Jurisdiction is a product feature here, not fine print, so we state the physical facts plainly. TLDBunker’s fleet runs on our own network and datacenter, which we will name here before launch. Those specifics are still pending only because the legal and infrastructure-reputation gates are open; they are not optional and they are not there to be left blank.

We think jurisdictional vagueness is a red flag in this market, and we refuse to trade on it. A host that will not tell you which network announces its IP space, or which region your data sits in, is asking you to guess about the one thing that determines your legal exposure. So before we take orders, both details above are filled in with a concrete autonomous system number and a named datacenter region — the same values you can confirm from the outside with a WHOIS or a routing lookup.

The people who run TLDBunker work under assumed pseudonyms. This is a deliberate design choice, not a disguise: a system administrator on the team is a named pseudonym, and we say so explicitly rather than dressing pseudonyms up as legal names. We borrow the model from Mullvad — the privacy of the operators is part of the threat model, and the way you build trust in a privacy host should never be “because we told you our names.”

Instead, we give you artifacts. Verify our work, not our identities:

• Public commits. Our policies, benchmark scripts and site content live in a public GitHub organisation. The history is real and inspectable — you can see what changed, and when.
• A published PGP key. By launch, our signing key signs the things that are supposed to be trusted: our transparency report and our benchmarks. If a signature does not verify against our published key, it did not come from us.
• Reproducible, PGP-signed benchmarks. We publish the raw results for our own machines with the scripts used to produce them, so you can re-run them and compare. Numbers you cannot reproduce are marketing; numbers you can are evidence.

Pseudonymity is not a license to invent. We hold ourselves to a hard line on manufactured credibility, because fabricating expertise or reputation is the same category of dishonesty as astroturfing — and it is exactly the thing that would make our privacy claims worthless.

So, concretely, on this site and across our network you will not find:

• stock photography or AI-generated headshots posing as our team;
• invented founder biographies, a fake company history, or a backdated “since 20XX” origin story;
• purchased or “aged” forum, Reddit or Hacker News accounts pretending to be long-standing community members;
• planted testimonials, fabricated star ratings, or reviews we wrote about ourselves.

Where we do have a presence — a forum account, a GitHub org, a support channel — the affiliation is disclosed openly (“staff @ TLDBunker”). Seniority and reputation get built the slow, honest way, or not at all. That is the cost of doing this white-hat, and we would rather pay it than counterfeit trust.

TLDBunker does not pretend to be an island. It is one of five sites published by the same editor: this provider, an independent comparator, a knowledge hub that sells nothing, and two gated market and vertical sites. We disclose that relationship up front rather than hoping you never notice it.

Because the comparator and the hub may link to us — and we may link back — those links matter for trust. Every cross-site link in our footer is marked rel="sponsored", so the commercial relationship is legible to you and to search engines. If you want the full map of who publishes what and why, it is all on one page.

See the whole network → Or start from the product: plans and pricing, the anonymous VPS overview, or no-KYC hosting.