Carrier-grade NAT (CGNAT) is why some connections cannot port forward, host a game server, or reach a home NAS from outside. This test detects your public IP and network automatically, then helps you classify your router WAN IP - the one piece of evidence that actually proves CGNAT - so you get a clear answer instead of a guess.
The same comparison works as a double NAT test. If your router WAN IP is a private address such as 192.168.x.x or 10.x.x.x, a second router sits in front of yours - usually the ISP modem - and it blocks port forwarding the same way CGNAT does, but you can fix it yourself.
The public IP is what the internet sees; your router WAN IP is what proves CGNAT. Compare them before changing port-forwarding rules.

Detecting your public IP...
Your browser can't see your router's WAN IP directly, so paste it once and we'll do the rest. It is classified on your device and never sent anywhere.
For inbound access you need a VPN with port forwarding - a standard one hands you another shared address. For privacy alone, any trusted VPN hides your IP from the sites you visit.
Affiliate link. IP Trackers may earn a commission if you buy through it, at no extra cost to you. It does not change what we recommend - see our editorial policy.
It is free with no sign-up. A small contribution helps keep the checker running and the troubleshooting guides current.
A browser cannot read your router's WAN IP on its own, so a fully automatic one-click verdict is not technically possible. The honest, accurate approach is a two-part check:
100.64.0.0/10, we flag the rare carrier-level CGNAT case immediately.The decisive signal is simple: if the router WAN IP is in 100.64.0.0/10 and your public IP is different, you are behind CGNAT. For the full background on that range, read the CGNAT IP range explainer.
Still stuck on inbound access after confirming CGNAT? The port forwarding under CGNAT guide walks through every realistic fix.