Tool

Timezone and IP mismatch checker

Compare browser timezone, primary language region, and edge IP country to catch inconsistent QA presets.

Interactive diagnostic dashboard

Advanced browser signal auditor

QA scenario controls

Optional checks run only after consent and use the current browser session.

Data use: the scan reads browser-visible signals in this tab and calls the edge IP endpoint. JSON download is local. Share stores a redacted report for seven days by default and removes raw IP from stored report JSON.

Audit scan engine idle

Start a scan to inspect browser-visible signals, edge geography, language, timezone, storage, rendering, and optional WebRTC state.

How do you detect a timezone/IP mismatch?

Compare the browser timezone returned by `Intl.DateTimeFormat`, the primary language region, and Cloudflare edge IP country. A mismatch appears when those signals point to different regions.

Why does this matter for Playwright?

Playwright can set `locale`, `timezoneId`, and geolocation independently. If the network path is in a different country, region-sensitive tests may pass locally but fail in production-like traffic.

What should be fixed first?

Fix the network route and timezone first, then align locale and geolocation. Browser-level language settings are less useful if the edge country and timezone already contradict each other.

Limitations

Multi-country timezones, travel scenarios, corporate networks, and VPN exits can be legitimate. Use the mismatch as a QA review trigger, not as a user classification decision.