$bulletproof_stack

// layer 1 — the domain

Domains that don't get seized

Why your domain went down, where the attack came from, and which registrars + TLDs actually push back.

Why domains fall

Registrar suspends on a single complaint email

GoDaddy, Namecheap and Cloudflare Registrar forward every DMCA, abuse and TOS complaint by default. One template letter from a copyright bot, one report from a competitor with a paralegal, one angry user emailing abuse@ — they suspend first and tell you to argue from the takedown queue. No court, no judge, no notice period.

UDRP from a trademark holder

Any holder of a registered mark can file a UDRP via WIPO or NAF. Three-panelist administrative tribunal, no hearing, ~60 days to transfer order. Affiliate landings with a brand keyword in the domain lose by default — UDRP doesn't recognize fair use, it's a trademark-only forum. Hits every gTLD (.com, .net, .org, .info, .biz, .xyz, .shop, .store). .is, .ru, .to, .ch never opted in.

ICANN compliance attack on your WHOIS

Procedural takedown: anyone emails ICANN compliance claiming your WHOIS data is inaccurate (and it usually is, because privacy). ICANN orders the registrar to verify. You have 15 days to respond — typical, the email goes to the WHOIS contact which is fake — and the domain suspends automatically. Costs the complainant zero dollars. Only applies to gTLDs, not ccTLDs outside ICANN's contractual reach.

Authoritative DNS provider pulls the records

Domain still registered, registrar still on your side — but if your nameservers are at Cloudflare DNS, AWS Route 53, or any DNS host under cooperative jurisdiction, a subpoena or TOS complaint can make them remove your records. The domain technically still exists, resolves to NXDOMAIN, campaign goes dark. Most operators forget DNS is a separate chokepoint from the registrar.

Proxy / CDN provider drops the proxy and leaks the origin

Orange-cloud through Cloudflare, proxy through Bunny.net or any CDN. The proxy operator sees every request, gets subpoenaed, gets a TOS complaint, drops the proxy. When the proxy disappears the A record reverts to the raw origin IP — your supposedly-bulletproof VPS now sits in the open, DDoS-exposed and identifiable. The proxy drop is what turned dozens of "bulletproof" stacks into doxed stacks in 2022–2024.

Registry-level state seizure

Verisign runs .com under US law. US ICE has seized thousands of .com domains under counterfeit-goods and unlicensed-gambling theories. Same dynamic everywhere: .uk under Nominet under UK law, .de under DENIC under German law. Once the registry is court-ordered, no registrar downstream has standing to refuse. .is under ISNIC has effectively zero seizure history for commercial speech; .ch and .to are similar. Your TLD choice is your defense here.

Where the attack happens

Top-down by who can hit you, from the global root to the closest layer. Each actor is a separate chokepoint — hardening one without the others is wasted work.

  1. 1

    ICANN — the global root

    Sets the rules every gTLD registry has to follow: UDRP, mandatory WHOIS accuracy, the contracts registrars sign. ICANN doesn't suspend domains directly but its policies are why UDRP exists at all and why the WHOIS-accuracy attack works. ccTLDs (.is, .ru, .to, .ch) sit outside ICANN's contractual reach and don't have to honor UDRP. This is the single biggest reason to pick a ccTLD over a gTLD for anything sensitive.

  2. 2

    Registry — operator of the TLD

    Whoever runs the TLD on the wire: Verisign for .com, ISNIC for .is, Nominet for .uk. Subject to the law of the country the registry operates from. Can suspend or seize a domain regardless of what your registrar wants — Verisign honors US ICE orders, ISNIC won't honor a foreign court. Your TLD choice = your registry choice = your top-of-stack jurisdiction. Pick the country first, then the registrar.

  3. 3

    Registrar — where you bought it

    Your direct point of contact: payment, WHOIS, suspension orders. In practice the registrar is the one who pulls the plug when a complaint lands. GoDaddy, Namecheap and Cloudflare Registrar forward everything by default. Njalla, 1984 Hosting, FlokiNET and OrangeWebsite publish policies of pushing back, and they live in Sweden / Iceland / Romania where they can legally refuse routine foreign complaints.

  4. 4

    WHOIS exposure

    Separate attack vector from suspension. If WHOIS shows your real name and address, anyone can sue you directly, dox you on social media, or feed the data to a takedown-as-a-service operator. Fix is two layers deep: WHOIS-privacy-by-default at registrar level (Njalla, 1984, OrangeWebsite all ship it), and registry-level privacy at TLD level — .is doesn't publish anything, which is the strongest WHOIS posture money can buy.

  5. 5

    Authoritative DNS provider

    Whoever runs your nameservers can take your domain dark even if it's still registered. Cloudflare DNS sits under US subpoena; AWS Route 53 same; even some "privacy" DNS hosts cave on a formal court order. Cleanest move: nameservers at the same privacy-friendly registrar (Njalla and 1984 both run DNS), at a separately-vetted privacy-friendly DNS operator, or your own nameservers on a bulletproof VPS.

  6. 6

    Proxy / CDN provider (different from DNS — read this twice)

    The mistake most operators make: assuming DNS at a friendly host means safe. Your A records can still point through Cloudflare's orange cloud, Bunny.net, or any proxy CDN — and every visitor request flows through that proxy operator. They see traffic, can be subpoenaed, can drop the proxy on TOS. When they drop it the next DNS lookup exposes your raw origin IP in cleartext — and that origin is often the bulletproof VPS you carefully chose, now DDoS-exposed and doxable. DNS provider and proxy provider are two separate decisions; treat them as such.

What to actually do

If everything above scared you, this is the order to set up a domain that actually survives. Skip steps and the chain breaks at the weakest link.

  1. 01

    Pick the TLD before you pick the registrar

    Anything sensitive → ccTLD outside ICANN's contractual reach: .is, .ch, .li, .to. Avoid .com, .net, .org, .info, .biz, .xyz, .shop — every one of these is exposed to UDRP and to ICANN compliance attacks. If SEO forces you into a gTLD, accept that UDRP is your top operating risk.

  2. 02

    Register with a published DMCA-ignore registrar, pay in crypto

    Njalla, 1984 Hosting, OrangeWebsite, FlokiNET, Virtualine, BPW and BPServ all publish a "we don't forward routine complaints" stance and accept BTC or Monero. Pay in crypto so there's no card or bank trail tied to your domain payment.

  3. 03

    Turn WHOIS-privacy on, or use a registry that doesn't publish

    Njalla, 1984 and OrangeWebsite ship WHOIS-privacy by default. .is at the ISNIC registry doesn't publish WHOIS at all — the strongest posture you can buy. Without this step, anyone can sue you on your real name in your local court.

  4. 04

    Run authoritative DNS at the registrar or self-host it

    Don't hand DNS to Cloudflare or AWS just because it's free. Njalla and 1984 both operate their own DNS. If you self-host, run it on a bulletproof VPS — same jurisdiction logic as the registrar.

  5. 05

    Make an explicit decision about proxy / CDN — never default to Cloudflare orange-cloud

    Two valid paths: (a) no public proxy, VPS direct, accept DDoS exposure; (b) a CDN aligned with the rest of the stack — BlazingCDN, X4B and other offshore-DDoS providers explicitly market to high-risk verticals. Cloudflare orange-cloud is the single most common way "bulletproof" setups get doxed.

  6. 06

    Keep the WHOIS contact reachable + pre-register 2-3 backup domains

    ICANN compliance gives you 15 days to respond to a WHOIS verification request — make sure that inbox is monitored. Separately, when the live domain falls you have zero hours of prep time: have alternatives pre-registered at the same registrar with DNS records pre-staged so a swap takes minutes, not days.

TLD comparison

Which top-level domains sit outside easy takedown jurisdictions, ordered by how rarely their registries comply with foreign requests.

TLDRegistryCountrySeizuresGood for
.isISNICIcelandEffectively neverAnything sensitive
.chSWITCHSwitzerlandVery rareAnything sensitive
.liSWITCHLiechtensteinEffectively neverAnything sensitive
.toTonic CorpTongaRareMost categories
.ruCoordination CenterRussiaZero (for Western)Watch sanctions exposure
.seIISSwedenRareMost categories
.comVerisignUnited StatesCommonAvoid for sensitive offers

Registrar comparison

Of the registrars on the directory, these are the ones an affiliate running sensitive offers actually uses. Sorted by how stubbornly they resist routine takedown letters.

RegistrarJurisdictionKYCAcceptsPriceRatingVisit
Virtualine
No-KYC domain registration, accepts Monero
MultipleNo KYCBTC · XMRFrom $10/year4.4Visit
Njalla
Njalla owns the domain — you use it
SwedenNo KYCBTC · LTC · XMR +1From €15/year (.com)4.2Visit
1984 Hosting (registrar)
Iceland-based registrar, crypto pay, you stay registrant
IcelandEmail onlyBTC · LTC · XMRFrom €15/year4.0Visit
OrangeWebsite
Free-speech hosting and registrar in Iceland
IcelandEmail onlyBTC · LTC · BCHFrom €15/year3.8Visit
BPW (registrar)
Domain registration tied to BPW's VPS line
SeychellesNo KYCBTC · Paymeer · WebmoneyBundled with VPS — confirm price at order3.7Visit
BPServ (registrar)
Anonymous domain registration, crypto checkout
Multiple — operator HQ unpublishedEmail onlyBTC · LTC · + altcoins.com from $30/year3.5Visit
BingLoft (registrar)
Indian commercial registrar, mainstream payments
IndiaLight KYCVisa · MC · PayPal +3Pricing not published — confirm at order3.0Visit