Public IP

User-Agent

LanguageTimezonePlatform

IP and User-Agent inspection

Review current browser IP, User-Agent, language, and timezone values to reproduce environment-specific issues.

Collect support details

Gather the browser string, language, and timezone that support or QA teams need for reproduction.

Check network path

Confirm the externally visible IP when using a VPN, proxy, office network, or mobile network.

Copy-ready environment data

Use the values in logs, support tickets, and QA notes after reviewing what should be shared.

How to use it

Open the page and inspect the current browser environment values.

Refresh after changing VPN or network settings to compare the visible IP.

Record User-Agent, browser language, and timezone when asking someone to reproduce a bug.

Before sharing, decide whether exposing IP or internal network details is appropriate.

Real input and output

Reading a User-Agent string

Input

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Output

Browser Chrome 131
OS macOS
Engine WebKit/Blink

Errors you will hit

The IP does not match your location

A VPN, corporate proxy, or mobile carrier NAT shows the exit server address. IP-based geolocation is indicative only.

The OS version is frozen at 10_15_7

Chrome reduces the detail it reports in the User-Agent for privacy. Newer macOS versions still report 10_15_7, so use Client Hints when you need the real version.

Things to check

IP is not exact location

IP-based location can differ from physical location because of VPNs, proxies, carriers, and office networks.

User-Agent is reduced

Modern browsers may reduce or freeze User-Agent details for privacy. Feature detection is more reliable for capability checks.

Tools that pair well