CryptoServers

匿名 VPS 主机—— 「匿名」的真实含义

"Anonymous" is not the same as "private", and neither is the same as "no-KYC". Anonymity is operational — you cannot be identified as the operator from the available data. Privacy is contractual — the provider commits not to share what they know. No-KYC is a specific subset of anonymity at the signup layer. All three matter; most hosting marketing conflates them. This page separates them, and walks the four layers of VPS anonymity that actually determine your exposure.

无需身份证 接受 XMR / BTC Tor 友好 可选账户
Anonymous VPS hosting

四个层次 VPS 匿名性

Anonymity does not live in one place; it lives in four. Two are the provider's job, two are yours. Cryptoservers handles the first two structurally; the second two require operational discipline that no provider can do for you.

1注册数据——服务商询问的信息

The information collected when you create the relationship: email, name, address, phone, ID document, billing details. Cryptoservers asks for a single field — a working email — and never validates name, address or phone because they are not collected. The signup form is two dropdowns and an email box. Nothing is enriched against third-party databases. This is the no-KYC layer; it is necessary but not sufficient for anonymity.

2支付痕迹——资金揭示的信息

Every payment leaves a trace somewhere. A card creates a chargeable record at your issuing bank. A bank wire creates a SWIFT log. Bitcoin creates a public UTXO graph. Monero creates an opaque commitment with no source visible. Cryptoservers accepts seven cryptocurrencies; XMR is the only one with protocol-level privacy at the payment layer. BTC, LTC, ETH, BCH, DOGE, DASH are pseudonymous — strong if you use fresh wallets, weak if you withdraw directly from a KYC exchange. We never accept fiat, so card-network surveillance is structurally absent.

3网络活动——您如何访问 VPS

Every SSH session and panel login leaves a trace at your end. If you SSH from a residential IP that your home ISP can attribute to you, the network-layer anonymity is gone regardless of what the VPS knows. Cryptoservers does not block Tor or VPN traffic on the deploy form, the panel or the VPS itself; the operational discipline of routing through Tor (Tor-only or Tor → VPN → SSH) is yours to maintain. We do log panel session IPs for 24 hours for brute-force protection — short retention, deliberately limited scope.

4运营元数据——日志、工单等细节

The text of support tickets, the contents of abuse reports filed against you, the workload running on the VPS, the public IP your services bind to, and any leaks the workload itself produces (banner strings, login fingerprints, SSL certificates, EXIF data, analytics cookies). Tickets and abuse correspondence are subject to our 90-day retention; the workload's leaks are out of our hands. This is the layer most users underestimate, and the one a determined adversary will go after first.

What's anonymous, what's not

流经 Cryptoservers VPS 每类数据的平铺表格及我们的处理方式。无营销内容:仅三列——我们看到的、我们记录的、我们共享的。

层次 我们看到的 我们记录的 我们共享的
注册邮箱 您提交的地址 存储于客户记录 仅在有效本地法院命令下
真实姓名 / 身份证 / 手机号 无——从未收集 无——从未收集 无法共享从未拥有的数据
支付 链上交易 ID、收款地址、金额 账单行 + 交易 ID,7 年(公司法) 仅在有效本地法院命令下
控制面板会话 IP 登录来源 IP 24 小时(防暴力破解) 仅在有效本地法院命令下
控制面板操作 开通 / 重启 / 重建 / 快照 90 天(滥用/安全) 仅在有效本地法院命令下
到您 VPS 的 SSH 连接 无——在虚拟机内部终止 无——不在主机上 Cannot share what we don't see
客户网卡流量 仅按端口字节计数 无网络流量记录,无数据包捕获 无数据可共享
支持工单 您发送给我们的内容 2 年(服务连续性) 仅在有效本地法院命令下

运营卫生习惯 提示

The provider can clean up layers 1 and 2; you have to clean up 3 and 4. Below: the discipline that makes the difference between "anonymous on paper" and "anonymous in practice".

网络使用规范:

  • Reach the deploy form, the panel and the VPS through <strong>Tor</strong>. The deploy form works under Tor without modification; we do not show a CAPTCHA, do not block Tor exits and do not enrich the source IP. For SSH, Tor → SOCKS5 → ssh is the cleanest chain (use <code>torsocks ssh</code> or <code>ProxyCommand nc -X 5 -x 127.0.0.1:9050 %h %p</code>).
  • Or run <strong>Tor → VPN → SSH</strong> if you need a stable exit IP for a service that does not tolerate the Tor exit pool. Pay the VPN in Monero, use a separate VPN per VPS.
  • Avoid SSHing in directly from a residential ISP-attributable IP. Do it once and your ISP's NetFlow logs (which you do not control) link the VPS public IP to your home circuit forever.

钱包使用规范:

  • Use a <strong>fresh wallet per invoice</strong> for Bitcoin payments, or pay in Monero (which makes "fresh wallet" the default rather than the exception).
  • If you must withdraw from a KYC exchange, route through a coinjoin (Wasabi, JoinMarket) or convert to Monero through a swap that does not require KYC.
  • Do not consolidate UTXOs from multiple Cryptoservers refunds back into a single wallet — keeping them unconsolidated is free privacy.

邮箱使用规范:

  • Use a <strong>separate email per VPS</strong>. SimpleLogin, AnonAddy and Proton aliases all work; so do disposable inboxes if you do not need to receive future emails after the deploy.
  • Do not link the VPS-purchase email to anything else — no other accounts, no recovery emails, no shared password manager entry that would correlate it with your real identity.

工作负载使用规范:

  • Audit what your <em>service</em> emits. Banner strings (<code>Server: nginx/1.24.0 (Ubuntu)</code>), HTTPS certificates (subjects with your real name), embedded analytics, EXIF in uploaded images, JS error trackers — all of these can re-identify you faster than the VPS provider can.
  • Strip metadata before publishing. Use <code>exiftool -all=</code> on images, <code>pdftk</code> for PDFs, and disable <em>any</em> third-party JS that phones home from a public site.

匿名 VPS 无法防御

The honest section. Anonymous VPS is a useful tool with a defined threat model. Below: the threats it does not address. If any of these match your adversary, layer the VPS with the additional defences mentioned.

直白说明: Anonymous VPS protects against "the hosting company knowing who you are." It does not protect against everyone else who might be watching the network or the workload. Threat-model accordingly.

全球被动对手。 A global passive adversary (GPA) — typically a signals-intelligence agency with broad network observation capability — can correlate Tor entry and exit timing, deanonymise long-lived flows by traffic-pattern analysis, and link your VPS public IP back through the Tor circuit to your residential ISP under sufficient observation density. Anonymous VPS does nothing to defeat a GPA. Defending against a GPA requires a different toolkit (Tails, mixnets, intermittent connectivity, OPSEC discipline far beyond hosting choice).

通过工作负载本身的旁信道。 If the public service running on your anonymous VPS leaks your identity through a login fingerprint, a unique writing style, an embedded analytics tag you forgot to remove, or a single tweet that mentions the IP — anonymity collapses regardless of how clean the VPS purchase was. This is the most common failure mode we see in post-mortem write-ups; the workload is the weakest link.

如果直接 SSH 连接,则有 ISP 级元数据。 Your home ISP records that you connected to the VPS public IP at this timestamp, this volume, this protocol. Even without packet capture, NetFlow-grade metadata is sufficient to link "VPS A made noise" with "subscriber X was online and connected to A at the same moment". The fix is not to SSH from a home connection: route through Tor or through a VPN you bought separately.

取证磁盘镜像。 A VPS lives on physical hardware in a rack. If the underlying disk is imaged through a court order or hypervisor introspection, anything you stored unencrypted is recoverable. Encrypt sensitive data at rest <em>inside the guest</em> with keys held by you (LUKS, dm-crypt with passphrase prompt at boot, file-level encryption like age or gocryptfs). The anonymity of the VPS purchase does not protect what is on the disk.

被强制披露邮件内容。 Your signup email, even on Proton or Tutanota, lives at a provider with its own jurisdiction and its own court-order obligations. If that provider is compelled to hand over inbox contents, they would include your Cryptoservers deploy emails (containing the VPS IP). PGP-encrypt mail-at-rest where possible; consider self-hosted mail behind Tor for the highest-paranoia profiles.

匿名 VPS 常见问题

Eight questions buyers and journalists ask us most about the anonymity properties of a Cryptoservers VPS.

What's the difference between an "anonymous VPS" and a "private VPS"?
Anonymity is operational — you cannot be identified as the operator from the available data. Privacy is contractual — the provider commits not to share what they know. They are different properties; you can have one without the other. Cryptoservers ships both: the no-KYC signup minimises what we collect (anonymity), and our Privacy Policy plus the warrant canary commit us to disclose only on valid local-jurisdiction process (privacy). Most providers conflate the two; we separate them on purpose.
If I sign up with a Proton email and pay in Monero, am I fully anonymous?
Mostly — but read the four-layer table on this page. The signup data layer is anonymised (Proton handle, no other identifiers), and the payment-trail layer is anonymised (Monero is private at protocol level). The two remaining layers — network activity and operational metadata — are operator-controlled. Your SSH source IP, the public IP your service runs from, your login fingerprint and any leaks from the workload itself can re-identify you regardless. Anonymity is layered.
Do you require an account, or is signup truly accountless?
Truly accountless. You can pay an invoice from /deploy/, receive SSH credentials by email and never log into the panel. The account exists if you want one (snapshots, dashboard, re-deploy buttons) but it is optional. A surprising number of long-tenure customers — including ones running 20+ VPS — have never claimed a panel account.
Can I use Tor to access the deploy form and the panel?
Yes, both work over Tor without modification. We do not block Tor exit IPs at the WAF and we do not show CAPTCHAs on legitimate Tor traffic. The panel session cookie is set on the response so the browser can keep you logged in across pages; everything else is HTML over HTTPS. We have a hidden-service mirror on the roadmap; the clearnet path over Tor is fully supported in the meantime.
Do you log SSH connections, panel logins or VPS console access?
We log panel actions (provision, reboot, rebuild, snapshot) for 90 days for abuse and security investigation, and panel session source IPs for 24 hours for brute-force protection. We do not log SSH connections to your VPS — those terminate inside your guest, not our infrastructure. NIC mirroring is off; we do not run netflow on customer traffic. Details and retention table are in the Privacy Policy.
Can my provider be compelled to identify me retroactively?
Only with the data we have. A binding court order from our jurisdiction (Saint Kitts and Nevis) or the local jurisdiction where the datacenter sits could compel us to disclose what we hold. What we hold for an anonymous-signup customer is: the email you signed up with, the on-chain transaction id of your payment, the deploy timestamps, and panel action logs (90 days). We do not have a name, an ID, a phone number or a billing address to disclose. Our warrant canary documents the count.
What about side-channel re-identification through my VPS's service?
This is the threat model most users underestimate. If the public website you host on the VPS leaks your real identity (login fingerprint, browser session, content metadata, EXIF, JS analytics that you forgot to remove, a single tweet that mentions the IP), the anonymity of the VPS purchase becomes irrelevant. The VPS is anonymous; the service running on it is whatever you configure it to be. Audit your workload, not just your provider.
Do you accept email aliases (SimpleLogin, AnonAddy, Proton aliases)?
Yes, all three plus self-hosted aliases and disposable inboxes. We do not validate domain reputation and we do not enrich the email address against any third-party database. The only requirement is that you can read the deploy email — anything that delivers SMTP works.

匿名 VPS, 在所述限制范围内。

五个级别,四个司法管辖区,无需身份证,无需手机号,账户可选,Tor 友好。支持七种币种支付。