Technical Specifications, Operational Constraints, and Protocol Boundaries.
Status: Verified_Information_Exchange
Provisioning typically completes in 60-90
seconds.
X402 utilizes high-speed NVMe backends. If pings are successful but SSH is refused,
the sshd daemon is still
initializing.
Give it 30 additional seconds.
X402 is a neutral proxy. We lease hardware in Germany, Finland, and the US. We maintain a Zero-Interference policy unless we receive valid legal abuse reports from upstream. Always keep off-site backups; entropy is the only constant.
Why not in-house? Physical hardware is a localized vulnerability. By acting as a Global Orchestrator, X402 can shift capacity between providers instantly if a jurisdiction becomes hostile to privacy.
Outbound traffic on Port 25 (SMTP) and 465 is hard-blocked. This ensures our IP mesh remains clean from spam-flagging. Technical agents should utilize third-party API relays for mail transmission.
Tor Guard/Middle Nodes: Permitted.
Tor Exit Nodes: Prohibited.
Exit node abuse notices risk the entire gateway.
Nodes detected as exits will be nuked without refund.
Valid DMCA complaints trigger an Immediate Nuke of the instance. Ephemeral nodes are not seedboxes. Do not attempt to host publicly tracked copyrighted material.
X402 is not "Managed Hosting." It is a raw technical gateway for developers and AI Agents. If you cannot handle a headless Linux terminal or SSH keys, seek an easier path.
Is this a honeypot? Probably not. But we encourage you to use LUKS encryption and fresh burner wallets. Trust the protocol, trust the math, never trust a provider.