Server network › Spain › Spain1
Spain1
Madrid, Spain
| Type | VPN |
|---|---|
| Continent | Europe |
| Country | Spain |
| Location | Madrid |
| Exit address | 31.70.133.178 |
| IPv6 | IPv4 only — the tunnel blocks client IPv6, so nothing leaks |
| Perfect forward secrecy | Yes — ephemeral keys per session (ECDHE) |
| WireGuard | Yes |
| Protocols | UDP 1194 · TCP 443 · WireGuard 51820 |
| OpenVPN | 2.7.8 |
| Kernel | 6.12.113+deb13-amd64 |
| Handshake | tls-crypt — the whole handshake is encrypted, so scanners see nothing |
| DNS pushed | 10.8.0.1 |
| P2P | Allowed |
| Access | All plans |
| Agent | 2.4.40 |
| Last report | just now |
| Link speed | 1000 Mbit/s |
Encryption
What this node negotiates. The control channel sets up the tunnel and proves the server’s identity; the data channel carries your traffic. Both are listed in the order the server prefers them.
OpenVPN control channel
TLS_AES_256_GCM_SHA384TLS_CHACHA20_POLY1305_SHA256TLS_AES_128_GCM_SHA256 OpenVPN data channel
AES-256-GCM
AES-128-GCM
CHACHA20-POLY1305
The first is what a current client will actually use; the rest are accepted for older clients. The server’s order decides, not the client’s.
WireGuard
ChaCha20-Poly1305
Curve25519
BLAKE2s
WireGuard has no cipher negotiation at all – one suite, fixed by the protocol, with new ephemeral keys about every two minutes.
Traffic, last 24 hours
peak 74.8 kbit/s · busiest 4 usersEverything on this page is reported by the node itself in its heartbeat, or derived from the same code that writes its configuration – nothing here is typed in by hand.