← DialectForge

What Your ISP Sees

A side-by-side comparison of network traffic captured by a packet analyzer — the same tool governments use to detect and block VPNs.

🔓 Standard VPN Identifiable

WireGuard Protocol
0000 01 00 00 00 a1 f2 c3 04 8b 7e 33 d1 5c a9 02 ef
0010 b7 44 19 e6 03 8d 71 fa 22 c0 15 ab 90 6d e8 3b
0020 f3 28 7c d5 4e 01 b9 87 63 ae 0f dc 76 5a e4 11
0030 00 00 00 00 00 00 00 00 d4 1b c7 52 38 f0 a6 9e
0040 04 00 00 00 a1 f2 c3 04 00 00 00 01 9c 47 b3 28
0050 7f e1 55 c8 0a 3d 96 bf 44 72 ed 18 a5 03 f7 61
0060 04 00 00 00 a1 f2 c3 04 b8 23 4f 91 de 60 c7 1a
0070 53 f9 82 d6 01 e4 70 bd 2c a8 0b ff 97 6e 43 a0
Protocol signature — WireGuard message type bytes, always identifiable
Known header fields — Sender index, counter, and handshake fields match a known pattern

🛡️ DialectForge Undetectable

dialect cycling
0000 74 24 9f c4 77 e3 22 1c b6 58 0d a3 f1 6b 89 3e
0010 d7 42 15 e8 93 af 5c 71 0e fa 36 c5 88 2d b4 60
0020 a2 17 cb 4e f5 63 8a d9 31 7c e6 04 bf 52 98 2b
0030 46 ed 81 3a c8 57 0b f4 6f a5 1e d3 79 40 bc 13
0040 e1 56 8c 2f da 68 a7 34 f0 4b 97 c2 1d b5 73 ee
0050 29 86 d0 4c fb 61 a4 38 c7 55 0a e9 72 b1 3d f8
0060 83 c6 1a 5f ae 47 d4 02 69 bb f7 2e 94 c1 58 0f
0070 e5 3b a0 76 d8 43 1f b9 64 fc 27 8e 51 cc 05 ab
Every byte is random — No signatures, no headers, no recognizable structure of any kind

Why does this matter?

Countries like China and Iran use deep packet inspection to fingerprint and block VPN protocols. If traffic has a recognizable pattern, it gets blocked. DialectForge traffic is indistinguishable from random noise — there's nothing to fingerprint.

And even if traffic were intercepted, injecting packets into a DialectForge stream has no effect — foreign data doesn't speak the dialect and is silently dropped.

↻ dialect refreshes every 2 minutes — patterns never persist