CGNAT Check

About the site

About CGNAT Check

CGNAT Check is a focused troubleshooting resource for people trying to understand why inbound connections, hosting, remote access, port forwarding, or open NAT are not working as expected.

Why the site exists

CGNAT Check is an independent utility focused on one troubleshooting problem: understanding why a home connection cannot accept expected inbound traffic. Port-forwarding problems are often described as a single router-setting issue, even though the real cause may be CGNAT, double NAT, the wrong WAN value, a local firewall, an inactive service, or a connection model that never used direct inbound traffic. The site keeps those related questions in one narrowly focused toolkit.

The aim is not to diagnose every home-network problem. It is to help a reader gather better evidence, distinguish common NAT topologies, and ask an ISP or equipment vendor a more precise question.

How the checker is interpreted

The checker compares the public IPv4 visible to the web server with the WAN IPv4 that the user manually reads from a router or gateway. Address ranges and exact public-IP matches provide useful signals, but the result remains best-effort because the browser cannot inspect every router or provider system in the path.

The complete methodology page documents how shared, private, matching, and mismatched address cases are handled and what the checker deliberately does not claim.

Worked examples are either clearly labelled illustrations or documented observations from development troubleshooting. For example, the mobile-hotspot guide records the exact laptop and gateway values observed in one Android tethering test and separates what those values established from what remained unknown.

Limits and verification standards

  • Browser-visible networking information cannot prove every ISP topology or policy.
  • Provider behavior may vary by plan, region, account, equipment, and over time.
  • ISP-specific claims are worded cautiously and should be confirmed with the provider.
  • A failed port test does not by itself prove CGNAT.
  • A clean address comparison does not prove that a firewall or forwarding rule is correct.
  • Mobile hotspots may not expose the carrier-facing WAN address needed for comparison.

Free troubleshooting comes first

The site prioritizes checks that do not require buying anything: identify the correct WAN IP, map the local router path, verify the service and firewall, ask the ISP about a public IPv4, and consider supported IPv6 or private-access approaches where relevant.

Paid workarounds are presented only in relevant contexts and after free options. No commercial product is described as a universal answer to CGNAT or inbound-connectivity problems.

Affiliate and advertising transparency

Some outbound links may be affiliate links. CGNAT Check may earn a commission when a reader purchases through one of those links, at no additional cost to the reader. The relationship is disclosed beside the recommendation.

Affiliate availability does not change the checker's IP classification, result wording, eligibility rules, free-first recommendation order, or documented methodology. Commercial relationships do not determine a technical result. Advertising configuration is separate from the technical tools and editorial explanations.

Corrections, policies, and contact

Router interfaces and provider policies can change. If a guide is inaccurate for current equipment, report the model, firmware or app version, the field label you observed, and which statement needs correction. Reports are reviewed against the site's cautious evidence standard rather than being turned into broad claims about every customer.

Read the privacy policy for information about request data and analytics, and the disclaimer for the limits of the tools and guides. Questions, corrections, or feedback can be sent through the details on the contact page.