What your public IP address says about your connection
Your public IP address is the address remote services see when traffic leaves your local network. It is useful for confirming routing, provider changes, VPN behavior, and whether support teams are looking at the right connection.
Public IP is different from local IP
Devices inside a home or office usually have private local addresses such as 192.168.x.x, 10.x.x.x, or 172.16-31.x.x. Those addresses are not normally visible to websites.
The public IP belongs to the route your traffic takes onto the internet. It may be assigned to your router, your mobile carrier, a VPN provider, or an upstream network using carrier-grade NAT.
Compare the browser result with the router WAN address
Open your router's internet or WAN status page using its documented management method. Compare its IPv4 address with the IPv4 result from the browser while using the same connection. Avoid comparing an IPv6 address with an IPv4 address; they are separate address families and need not follow identical routing.
A router WAN address in 100.64.0.0/10, which spans 100.64.0.0 to 100.127.255.255, is shared address space commonly used for carrier-grade NAT. The private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. A private WAN address can also mean that another router sits upstream. The browser result alone cannot distinguish these arrangements.
For an illustrative example, suppose the router shows 100.64.12.8 and a website shows 203.0.113.20. The latter is a documentation-only example address. The mismatch suggests upstream translation; ask your provider whether you have CGNAT before changing port forwarding. A normal forwarding rule on your own router does not configure the provider's upstream translator.
Provider and ASN data identify the network path
IP metadata services map addresses to network operators and autonomous system numbers. This can help show whether traffic is leaving through the expected ISP, a backup line, a mobile connection, or a VPN.
The organization name is not always the retail brand on your bill. Some providers use wholesale networks, parent companies, regional carriers, or cloud security platforms.
Location is approximate
IP-based location is an estimate based on registry and routing data. It can show the nearest city, a provider hub, or a commercial database location rather than your physical address.
A mismatch is common after provider changes, VPN use, mobile data, or newly reassigned IP ranges. It is usually a metadata issue unless location-sensitive services consistently route you to the wrong region.
Use a routing comparison without over-interpreting it
Record the displayed address and provider before changing the connection. If your organisation permits it, compare the same browser with and without its VPN, then restore the required setting. A corporate proxy, split tunnel, or IPv6 route can make different services see different addresses. A changed result tells you this request used a different exit; it is not a complete VPN leak test.
| Observation | Possible explanation | Next check |
|---|---|---|
| Address changes after switching on a VPN | This browser request may now leave through the VPN | Compare the provider and VPN's expected exit location |
| Provider name differs from your broadband bill | Wholesale carrier, parent company, proxy, or VPN | Check the router WAN status and provider documentation |
| City is wrong but country and provider are plausible | An approximate geolocation database entry | Report a persistent region problem to the affected service |
| Address changes after failover | Backup broadband or mobile route is active | Record the time and check any external allowlists |
Know where Port233's information comes from
The server uses the incoming request's network information to identify the address, then requests approximate metadata from the configured IP provider. Port233 supports IPinfo and ip-api, with a fallback when one provider fails. An address can remain visible even when city or provider metadata is unavailable; a missing field does not mean that your internet connection has failed.
A lookup does not identify a person, inspect devices on your LAN, reveal a street address, or prove that an incoming connection can reach your router. Do not publish a support screenshot containing your address unless it is necessary. Share it privately with the support team handling the issue.
When the address matters
Public IP details matter when diagnosing blocked services, allowlists, remote access, geolocation problems, suspicious route changes, and failover between multiple internet connections.
If you contact support, include the public IP, provider/ASN name, approximate location shown, time of test, and whether a VPN or mobile hotspot was active.
Sources and tool notes
The examples above are illustrative. The references below describe the tools and methods used. Read more about Port233-specific behaviour in our methodology and limitations.
Found a mistake? Send a correction with the page address and the result you expected. See our editorial approach.