# Check my browser, a troubleshooting page for OpenWAF Verify

> When the challenge page or the Verify widget fails, it links to verify.openwaf.dev, which says what blocks the check and gives a check ID for support.

[Check my browser](https://verify.openwaf.dev/) runs the checks OpenWAF Verify needs in the visitor's browser: JavaScript, Web Workers, the Verify files under `/__waf/challenge/`, access to your host, cookies, the system clock, the speed of the proof of work, automation and the network labels the edge sees (data centre, threat list). Each one says what it means and what to do. Then it runs the real widget and shows a check ID.

The [browser challenge](https://developers.openwaf.dev/waf/browser-challenge/), [under attack mode](https://developers.openwaf.dev/waf/under-attack/) and the [Verify widget](https://developers.openwaf.dev/waf/verify-widget/) now link to it when they fail («Trouble? Check your browser»), with your host and the challenge ID; not under an organization white-label brand. Your hosts answer a new `GET /__waf/challenge/v1/ping` for it.

Send the check ID to [support@openwaf.dev](mailto:support@openwaf.dev) within 7 days and we can see the results and what the failed challenge ran into. The record holds the network (/24 or /64), never the full IP address. See [Check my browser](https://developers.openwaf.dev/waf/verify-check/).