Skip to main content

WireGuard and AmneziaWG config validator

Review a client configuration before import. The parser stays in browser memory and checks [Interface], every [Peer], Address, DNS, Endpoint, AllowedIPs, PersistentKeepalive, MTU, duplicate peers and IPv4/IPv6 route coverage.

Validate locally

Processed locally. The configuration was not sent from this browser.

WireGuard guide

Ready. Maximum input size: 256 KB.

How to interpret the result

AllowedIPs = 0.0.0.0/0, ::/0 is a dual-stack full tunnel. Covering only IPv4 can leave IPv6 outside the tunnel; a full tunnel without DNS may leave name resolution on the original network. A split tunnel is not automatically wrong, but its routes should match your intention.

AmneziaWG uses additional obfuscation parameters. This validator identifies their presence and checks the shared WireGuard structure; use an AmneziaWG-compatible client for those profiles.

Advertisement

Frequently asked questions

Is the WireGuard PrivateKey uploaded?
No. The configuration is processed only by browser JavaScript and is not sent to PublicVPNList or analytics.
Does valid key syntax mean the key is safe?
No. Syntax only confirms the base64 shape. Treat every private key as a secret and rotate it if it has been shared.
What is the difference between full-tunnel and split-tunnel?
A full tunnel routes all covered IP families through the peer. A split tunnel routes only the networks listed in AllowedIPs.