Security · Request stopped

Sorry, your access to this site has been blocked

Your request was stopped by our security rules before it ever reached example.com. Nine times out of ten this is caused by something on your side: a VPN, a proxy, a browser extension, or an automated tool.

Reference ID
—
Your IP address
{{IP_ADDRESS}}
Event time (UTC)
—

Save the reference ID. It is the fastest way for our team to look up what happened to your request.

Try again
Why have I been blocked?

Our security layer is a firewall that sits in front of the whole site. It scores every incoming request and blocks the ones that look automated or abusive. Common triggers include:

  • A browser extension or user script replaying requests in a loop.
  • A VPN, Tor exit node, or shared proxy address that has been used abusively by someone else.
  • A scraper, headless browser, or CLI tool that does not run JavaScript or keep cookies.
  • An unusually large number of requests from your connection in a short window.
  • A shared or corporate network where a colleague tripped a rule first.
What can I do about it?
  1. Reload the page once. A rule can trip on a single malformed request and clear itself immediately.
  2. Turn off your VPN or proxy, or switch to a different network, then reload.
  3. Try a private window with extensions disabled to rule those out.
  4. If you are the site owner, check your firewall event log for the reference ID above.
  5. Still stuck? Email us with the reference ID and the exact time, and we will dig in.

Automated access that is expected and permitted should use the documented API endpoints rather than the public web pages.