Detects WebView, PWA and suspected virtual devices from the browser's own signals. Nothing is uploaded.
Find out whether a page is running inside an app's embedded browser, as an installed PWA, in a normal browser, or on a suspected virtual device — and what that changes.
Apps such as WeChat, Facebook, Instagram and TikTok open links in their own embedded browser (a WebView) instead of handing them to Chrome or Safari. The page looks the same, but the app controls the engine version, cookies, extensions and what the site can see.
It reads the User-Agent tokens that platforms add to WebViews (Android's "; wv)", iOS's missing Safari token), app-specific markers, standalone display mode for PWAs, and reuses the hardware-consistency signals from the fingerprint check to flag suspected emulators. Everything runs in your browser; nothing is uploaded.
Sites behave differently inside WebViews: logins fail, downloads are blocked, and fingerprints look odd because the engine is older or stripped down. Knowing where you are is the first step to fixing a page that "doesn't work".
On Android tap the ⋯ menu and choose Open in browser; on iOS tap share and choose Open in Safari. The check page shows the steps for your platform.
A mobile User-Agent combined with a software GPU renderer, no touch screen or impossible hardware values is what cloud phones and emulators look like. It is a suspicion, not proof — a real phone will not trigger it.
No. A PWA runs in your real browser engine in standalone mode without the address bar. The check tells the two apart.
