Home / Guides / VPS opsec mistakes
Guide

VPS opsec mistakes and how to avoid them.

A provider that knows nothing about you cannot help if you hand the link over yourself. These are the mistakes that most often connect a server to a person.

Identity reuse

  • The same username, email or avatar used elsewhere.
  • A writing style or signature phrase carried between identities.
  • Personal contact details in WHOIS, a certificate or a page footer.

Connection leaks

See hide your origin IP and VPS vs VPN.

  • Logging into the server or admin panel from your home IP while the site is meant to be separate.
  • A DNS record or certificate that points straight at the origin.
  • Mixing personal and project browsing in one browser profile.

Payment leaks

Read how payment works and paying with Monero.

  • Paying from an exchange account tied to your ID.
  • Sending the exact payment from a wallet used for other things.
  • Reusing one address on a public chain.

Metadata and files

  • Photos with location data in them.
  • Documents with author and company fields.
  • Backups with personal files included.

Server hygiene

Fix these with the hardening checklist and SSH keys and fail2ban.

  • Weak SSH setup and no updates.
  • Open database and admin ports.
  • Secrets in a public repository.

A quick pre-launch check

  1. Search your own identity details against the site.
  2. Check WHOIS and certificate fields.
  3. Check which IP your DNS reveals.
  4. Confirm which device and network you log in from.
  5. Review what is on the server that should not be.
FAQ

Common questions

What is the biggest opsec mistake?

Reuse. A single reused username or email can link an otherwise separate project to you.

Does RAM-only hosting fix these?

It limits stored data on the server after a reboot. It does nothing for your own habits. See RAM-only servers explained.

Keep reading

Related pages

Buy a VPS anonymously

Step-by-step: buy a VPS without an ID upload, pay in crypto, keep your access key safe and secure the server on day one.

Read more →

VPS hardening checklist: secure a new Linux server in 15 minutes

A practical checklist for a new Linux VPS: SSH keys, a non-root user, firewall, automatic updates and backups, with the commands.

Read more →

Privacy architecture

How AnonVPS is built to keep your data small: access-key sign-in, optional contact, RAM-only plans, encrypted storage and an honest threat model.

Read more →

Order a VPS paid in crypto.

Open the configurator