12-Point Opsec Checklist for an Anonymous Server That Holds

Twelve opsec controls for an anonymous server: alias, SSH keys, PTR, backups, XMR renewals. Each takes under an hour, each linking its matching VPSbit guide.
Twelve controls across account, access, network, data and payment: an alias that touches nothing else, keys-only SSH, neutral PTR, restic backups to a second box, XMR renewals from self-custody — each item sized under an hour.
12 locations · 19 coins · SLA 99.95% · no KYC · public canary
VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.
Launch nowThe 12 checks
- Email alias reserved for the hosting account alone — never reused anywhere else.
- Monero from self-custody — never an exchange withdrawal wired straight onto an invoice.
- SSH keys only, password auth disabled — plus a named sudo user rather than root.
- Default-deny firewall: allow the moved 22, 80/443, and only the service ports you truly run.
- fail2ban on top of the relocated SSH port — log noise falls by an order of magnitude.
- Unattended security upgrades enabled on the base OS.
- 2FA on the hosting panel, because the panel is attack surface in its own right.
- Panel over Tor/VPN — reach it through Tor or a VPN whenever local observers are part of the threat model.
- Neutral PTR/DNS — labels that carry neither names nor recognizable patterns.
- LUKS container wrapping data at rest (the walkthrough is in the full-disk encryption guide).
- Encrypted off-box backups — Restic or Borg pushed to a second VPS.
- Monthly review: fire the canary, audit the DNS records, rotate credentials.
What a skipped item costs
| Item you skip | How it usually breaks |
|---|---|
| #1 email | One breach ties every account together |
| #2 payments | A public BTC trail leads back to your exchange |
| #3/#5 access | Credential stuffing lands within days |
| #9 DNS/PTR | Old records keep naming you indefinitely |
| #11 backups | One ransom note or a wiped disk ends the project |
What the host covers — and what stays yours
Four of the twelve come covered on the hosting side: VPSbit asks for no documents, bills in crypto only, leaves the PTR editable and keeps no traffic logs beyond ≤24 h of connection metadata. The eight that remain are yours to implement, and each one has a matching guide on this site.
The full checklist — purchase through month one
- Dedicated privacy email; unique password; 2FA enabled.
- Checkout through Tor or VPN when local observers matter.
- Privacy flag (IS/CH) unless the latency model dictates otherwise.
- Pay XMR from self-custody; exact amount; one transaction.
- SSH keys only; passwords disabled; firewall default-deny.
- Neutral PTR; privacy DNS or none.
- Unattended upgrades; snapshot before risky changes.
- Encrypted offsite backups; prove a restore.
- Admin device habits kept apart from daily browsing.
- Re-read the limits page; check the warrant canary monthly.
Prime ($12) in Zurich is the default build with room to split services; Core serves when the checklist is followed ruthlessly on a single service. Ticking a list once is not opsec — schedules and renewals are where people slip.
Every line maps to something concrete in this catalog. The alias is what the panel account is built on; keys-only pairs with the firewall's default-deny; the neutral PTR is one panel edit because every server ships a dedicated IPv4 with an editable reverse record. Backups go over restic to a second box — a Summit dedicated with 2×2 TB of NVMe in a different city keeps the copy outside the app server's failure domain — and XMR renewals from self-custody delete the renewal-time identity check entirely. Checkout itself runs over Tor with no card form in the flow, connection metadata ages out inside 24 hours, and the warrant canary plus public status page give the monthly re-read something real to verify.
Print the list or keep it in an encrypted note. Blog posts skimmed once will not rescue you at renewal time.
Month-two additions: verify a backup restore into a second location, rotate SSH keys if any laptop left your control, confirm 2FA recovery codes still exist offline, and re-read the limits page once comfort sets in — comfort is when leaks creep in. Prime in Zurich at $12 remains the balanced default. When the checklist feels long, that is the price of private infrastructure; no shorter honest version exists.
Operational footnote: renewals and restores are where checklists die. Hold Prime in Zurich ($12) as the default, XMR for payments, Tor or VPN to the panel, and a tested backup. Re-read limits whenever safety starts feeling assured. Private infrastructure is a practice, not a purchase.
Final note: checklists expire at renewal and restore time. Prime $12 Zurich, XMR, Tor or VPN to the panel, tested backups, quarterly drills, the limits page reread when comfortable. Private infrastructure is practice. No shorter honest list exists.
Store 2FA recovery offline. Name servers generically inside password managers. If the alias provider itself dies, treat the panel as burned and migrate accounts. Boredom is the skill.
Checklist arrogance
High-risk nation-state models demand specialist advice beyond any VPS article. This checklist is a solid baseline for lawful private infrastructure — not a costume.
Month-two controls after the honeymoon ends
Past the first renewals: restore a snapshot into a second flag, rotate SSH keys whenever a laptop left your control, verify 2FA recovery still exists offline, and re-read the limits page while comfort persists. Prime ($12) in Zurich stays the balanced default; XMR for payments; Tor or VPN to the panel. Checklists fail at renewal and restore - calendar those drills or the day-one work evaporates.
Month-two proofs, not merely day-one ticks
Once the twelve items read green, prove them again: restore a backup into a second datacenter, rotate panel 2FA, verify the canary date, and re-scan PTR for name leaks. Prime ($12) in Zurich is the usual checklist home; Core serves a ruthless single-service operator. Schedules beat blog posts skimmed once.
Our own reference setup
Plan: Prime gives you 4 vCPU/8 GB — headroom for the LUKS container plus backup tooling at $12/mo. Location: Zurich. Read it next to the opsec guide and its honest limits.
An opsec-ready VPS in Zurich starts at $12/mo.
Launch nowMore rankings and guides
- Anonymous VPS opsec guide
- Limits of no-KYC anonymity
- How to buy an anonymous VPS
- how-to-pay-vps-with-monero
- Best privacy jurisdictions 2026
- VPS for a privacy tools stack
Are 12 items too many?
Each check is a one-time job of under an hour, while undoing even one miss costs far more. Calibrate the list to your threat model — but treat items 1–3 as non-negotiable.
How much of the list does the host cover?
On our side: no documents held, no traffic logged and PTR under your control. By design, access, DNS and backups never leave your hands — that division is the privacy model.
Where should backups land?
A second VPSbit machine on the same rails — Restic over SSH to Titan, 320 GB for $24/mo.
Does this checklist cover high-risk threats?
It is a solid baseline. Nation-state models call for specialist advice beyond a VPS article.
Monthly or annual billing?
Monthly billing trims large single-payment correlation; annual billing trims the invoice count - pick on purpose.
Primary sources
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.