# Block Pages: Which Anti-Bot System Is It?

> A dictionary of block pages: the status code, the words on the page, the header or cookie, and the anti-bot system behind each one, from Cloudflare to AWS WAF.

[Home](https://quanticdata.io/) / [Web Unlocker](https://quanticdata.io/web-unlocker/) / Block pages

Web Unlocker · Block pages

# Block pages: what you see, and which anti-bot system it is

A block page is what a site's protection sends instead of the page you asked for. This dictionary maps what you see, the status code, the words on the page, a header or a cookie, to the system that sent it, for eight systems from Cloudflare to AWS WAF, and links the page that explains each one.

[Start free](https://app.quanticdata.io/register?next=%2Funlock&utm_source=web-unlocker&utm_medium=website&utm_campaign=unlocker-guides&utm_content=block-pages-start-1) · [Read the docs](https://quanticdata.io/docs/#tag/Web-Unlocker/operation/unlockRequest)

- **88.9%**: calls answered with the real page across 27 protected targets, canary of 11 November 2026
- **81**: calls, 3 runs, default settings
- **4.1 s**: median response across the run

- [By the words](https://quanticdata.io/web-unlocker/block-pages/#words)
- [By status code](https://quanticdata.io/web-unlocker/block-pages/#status)
- [By header or cookie](https://quanticdata.io/web-unlocker/block-pages/#marks)
- [How to read a block](https://quanticdata.io/web-unlocker/block-pages/#rules)
- [Let the answer name it](https://quanticdata.io/web-unlocker/block-pages/#call)
- [Method](https://quanticdata.io/web-unlocker/block-pages/#method)
- [FAQ](https://quanticdata.io/web-unlocker/block-pages/#faq)

## Find it by the words on the page

Start with the sentence on the page: each system prints its own, and it is the most reliable mark. Search this table for the words you see.

| What the page says | System | What it means | Explained on |
| --- | --- | --- | --- |
| "Just a moment..." with "Verifying you are human" or "Checking your browser" | Cloudflare | A challenge page. A script checks the browser, then lets the request through. | ["Just a moment..."](https://quanticdata.io/web-unlocker/cloudflare-just-a-moment/) |
| "Verify you are human", with a box to tick or a spinner | Cloudflare | Turnstile, Cloudflare's check in place of a CAPTCHA: inside a challenge page, or as a widget on a form. | [Cloudflare Turnstile](https://quanticdata.io/web-unlocker/cloudflare-turnstile/) |
| "Error 1020" and "Access denied" | Cloudflare | A security feature set up by the owner of the site blocked the request. A refusal, not a check. | [Error 1020](https://quanticdata.io/web-unlocker/cloudflare-error-1020/) |
| "Error 1015" and "You are being rate limited" | Cloudflare | The address sent more requests than the rule of the site allows in a period. Temporary. | [Error 1015](https://quanticdata.io/web-unlocker/cloudflare-error-1015/) |
| "Sorry, you have been blocked", with a Ray ID | Cloudflare | A block by a security rule of the site, shown on Cloudflare's standard block page. A refusal, not a check. | [Cloudflare guide](https://quanticdata.io/web-unlocker/bypass-cloudflare/) |
| "Error 1005", "1006", "1007", "1008", "1009" or "1010" | Cloudflare | A ban set by the owner of the site: on the network (1005), the IP address (1006, 1007, 1008), the country (1009) or the browser's signature (1010). | [Cloudflare guide](https://quanticdata.io/web-unlocker/bypass-cloudflare/) |
| "Please enable JS and disable any ad blocker" | DataDome | The DataDome block page. In a browser a device check or a slider follows. | ["Please enable JS and disable any ad blocker"](https://quanticdata.io/web-unlocker/please-enable-js-and-disable-any-ad-blocker/) |
| "Access Denied. You don't have permission to access ... on this server." and "Reference #18." | Akamai | An Akamai edge server refused the request before the site saw it. | ["Access Denied ... on this server"](https://quanticdata.io/web-unlocker/access-denied-on-this-server/) |
| "Press & Hold to confirm you are a human (and not a bot)" | PerimeterX (HUMAN) | A behaviour challenge: the page records how the button is held. | [Press and hold CAPTCHA](https://quanticdata.io/web-unlocker/press-and-hold-captcha/) |
| "Access to this page has been denied", as the page title | PerimeterX (HUMAN) | The title of the same Press & Hold page. | [Press and hold CAPTCHA](https://quanticdata.io/web-unlocker/press-and-hold-captcha/) |
| "Pardon Our Interruption" | Imperva | The check of Imperva Advanced Bot Protection: the browser has to prove itself. | ["Pardon Our Interruption"](https://quanticdata.io/web-unlocker/pardon-our-interruption/) |
| "Request unsuccessful. Incapsula incident ID:" and a number | Imperva | A refusal by Imperva's firewall layer, before any script runs. | [Imperva (Incapsula) guide](https://quanticdata.io/web-unlocker/bypass-imperva/) |
| "The requested URL was rejected. Please consult with your administrator. Your support ID is:" | F5 BIG-IP | The blocking page of the firewall: a rule of the site's policy fired. | ["The requested URL was rejected"](https://quanticdata.io/web-unlocker/request-rejected-support-id/) |
| "Please enable JavaScript to view the page content." | F5 BIG-IP | The JavaScript check of bot defense. In a browser it reloads by itself. | [F5 BIG-IP and Shape guide](https://quanticdata.io/web-unlocker/bypass-f5/) |
| "Let's confirm you are human", with a puzzle | AWS WAF | The CAPTCHA action of a rule. | [AWS WAF guide](https://quanticdata.io/web-unlocker/bypass-aws-waf/) |
| "403 Forbidden" alone, or "The request could not be satisfied. Request blocked." | AWS WAF | A rule blocked the request outright. | [AWS WAF guide](https://quanticdata.io/web-unlocker/bypass-aws-waf/) |
| "I'm not a robot" with a box to tick, or pictures to pick from | reCAPTCHA or hCaptcha | A captcha widget that the site added to a page or a form, not a system in front of the site. | [CAPTCHA when scraping](https://quanticdata.io/web-unlocker/captcha-when-scraping/) |
| No words at all: a blank page that holds one script | Kasada or AWS WAF | A check that only a browser can run. The status code tells the two apart: see the next table. | [Kasada guide](https://quanticdata.io/web-unlocker/bypass-kasada/) |

![How the block page dictionary works: first three things you can see in a blocked answer, a 403 with the words Just a moment, a 429 with an empty page, and a 200 with the words Request Rejected, then a table that looks them up, last a card that names the system behind each one: Cloudflare, Kasada, F5 BIG-IP, and AWS WAF for a 202 or a 405.](https://quanticdata.io/web-unlocker/block-pages/diagram.webp?v=20261111b1)

*What you see in a blocked answer and the system behind it.*

## Find it by the status code

The status code alone is ambiguous. Read it together with what comes with it: the same code means different things on different systems.

| Status | What comes with it | System | What it means | Explained on |
| --- | --- | --- | --- | --- |
| `403` | "Just a moment..." and the header `cf-mitigated: challenge` | Cloudflare | A challenge. A browser passes it; an HTTP client stays on the `403`. | ["Just a moment..."](https://quanticdata.io/web-unlocker/cloudflare-just-a-moment/) |
| `403` | "Error 1020" | Cloudflare | A flat refusal by a rule of the site. | [Error 1020](https://quanticdata.io/web-unlocker/cloudflare-error-1020/) |
| `403` | A tiny page: one sentence and a script from `captcha-delivery.com` | DataDome | The block page, with a device check or a slider behind it. | ["Please enable JS and disable any ad blocker"](https://quanticdata.io/web-unlocker/please-enable-js-and-disable-any-ad-blocker/) |
| `403` | "Access Denied" and a Reference line | Akamai | A refusal at the edge server. | ["Access Denied ... on this server"](https://quanticdata.io/web-unlocker/access-denied-on-this-server/) |
| `403` | "Press & Hold", or JSON with `appId` on an API call | PerimeterX (HUMAN) | The challenge page, or its JSON form. | [Press and hold CAPTCHA](https://quanticdata.io/web-unlocker/press-and-hold-captcha/) |
| `403` | "Incapsula incident ID" | Imperva | A refusal by the firewall layer. | [Imperva (Incapsula) guide](https://quanticdata.io/web-unlocker/bypass-imperva/) |
| `429` | "Error 1015" | Cloudflare | A real rate limit, set by the owner of the site. | [Error 1015](https://quanticdata.io/web-unlocker/cloudflare-error-1015/) |
| `429` | An almost empty page that loads `ips.js`, on the very first request | Kasada | Not a rate limit. Every new visitor gets it until a browser runs the script. | [Kasada guide](https://quanticdata.io/web-unlocker/bypass-kasada/) |
| `202` | An almost empty page and the header `x-amzn-waf-action: challenge` | AWS WAF | The Challenge action: a silent script, then the page reloads. | [AWS WAF guide](https://quanticdata.io/web-unlocker/bypass-aws-waf/) |
| `405` | A puzzle page and the header `x-amzn-waf-action: captcha` | AWS WAF | The CAPTCHA action, not a wrong method. | [AWS WAF guide](https://quanticdata.io/web-unlocker/bypass-aws-waf/) |
| `200` | "Request Rejected" and a support ID | F5 BIG-IP | A rejection served as a normal answer. | ["The requested URL was rejected"](https://quanticdata.io/web-unlocker/request-rejected-support-id/) |
| `200` | "Pardon Our Interruption", or a page that holds only a frame from `/_Incapsula_Resource` | Imperva | A check served as a normal answer. | ["Pardon Our Interruption"](https://quanticdata.io/web-unlocker/pardon-our-interruption/) |
| `503` | "Just a moment..." on older setups | Cloudflare | An older JavaScript challenge. | ["Just a moment..."](https://quanticdata.io/web-unlocker/cloudflare-just-a-moment/) |

## Find it by a header or a cookie

When the page says nothing, the headers and the cookies still do. Most of these marks say which system is in front of the site, not that it stopped you: only the two response headers that name an action say that.

| Header or cookie | Where | System | What it tells you | Explained on |
| --- | --- | --- | --- | --- |
| `cf-mitigated: challenge` | Response header | Cloudflare | This answer is a challenge page, not the page you asked for. | ["Just a moment..."](https://quanticdata.io/web-unlocker/cloudflare-just-a-moment/) |
| `server: cloudflare`, `cf-ray` | Response headers | Cloudflare | The site is behind Cloudflare. Present on every answer, blocked or not. | [Cloudflare guide](https://quanticdata.io/web-unlocker/bypass-cloudflare/) |
| `cf_clearance`, `__cf_bm` | Cookies | Cloudflare | A passed challenge, and bot scoring. | [Cloudflare guide](https://quanticdata.io/web-unlocker/bypass-cloudflare/) |
| `challenges.cloudflare.com` | Script host | Cloudflare | Turnstile is on the page, as a widget or inside a challenge. | [Cloudflare Turnstile](https://quanticdata.io/web-unlocker/cloudflare-turnstile/) |
| `x-datadome`, `datadome` | Response header, cookie | DataDome | The site is protected by DataDome; the cookie is checked on every request. | [DataDome guide](https://quanticdata.io/web-unlocker/bypass-datadome/) |
| `_abck`, `bm_sz`, `ak_bmsc` | Cookies | Akamai | Akamai Bot Manager is judging the client; `_abck` holds the verdict. | [Akamai Bot Manager guide](https://quanticdata.io/web-unlocker/bypass-akamai/) |
| `_px3`, `_pxvid`, `_pxhd` | Cookies | PerimeterX (HUMAN) | The session is scored; `_px3` carries the score. | [PerimeterX (HUMAN) guide](https://quanticdata.io/web-unlocker/bypass-perimeterx/) |
| `x-kpsdk-ct`, `x-kpsdk-cd`, `KP_UIDz` | Request headers, cookie | Kasada | The tokens a browser adds after Kasada's script ran. | [Kasada guide](https://quanticdata.io/web-unlocker/bypass-kasada/) |
| `x-iinfo`, `x-cdn: Imperva`, `visid_incap_`, `incap_ses_`, `reese84` | Response headers, cookies | Imperva | The site runs behind Imperva; `reese84` belongs to the bot check. | [Imperva (Incapsula) guide](https://quanticdata.io/web-unlocker/bypass-imperva/) |
| `TS` cookies, `TSPD_101`, `BIGipServer` | Cookies | F5 BIG-IP | A BIG-IP firewall is in front of the site. | [F5 BIG-IP and Shape guide](https://quanticdata.io/web-unlocker/bypass-f5/) |
| `x-amzn-waf-action`, `aws-waf-token` | Response header, cookie | AWS WAF | The action a rule took, and the token that proves a passed challenge. | [AWS WAF guide](https://quanticdata.io/web-unlocker/bypass-aws-waf/) |
| `g-recaptcha`, `h-captcha` | Element in the page | reCAPTCHA, hCaptcha | A captcha widget is on the page. It may never show a challenge. | [CAPTCHA when scraping](https://quanticdata.io/web-unlocker/captcha-when-scraping/) |

## How to read a block

- **The status code is not proof.** Imperva and F5 BIG-IP often serve their block page with `200`. Kasada answers a new visitor with `429` before any rate was exceeded. On AWS WAF a `405` is a puzzle, not a wrong method. Code that trusts the status stores block pages as data.
- **The words are the best proof.** Every system prints its own sentence, and sites rarely change it. One line of the body is enough to name the system: a reference, a support ID, an incident ID, a title.
- **A mark is not a block.** A cookie or a header says which system is in front of the site. It is on the answers that pass as well as on the ones that are stopped, so check the body before you call an answer blocked.

## If you are a visitor

If you met one of these pages in your browser, the first steps are nearly always the same: JavaScript and cookies on, ad blockers and VPN off for that site, a normal up-to-date browser, one reload. When the page prints a reference, a Ray ID or a support ID, send it to the site: only its team can read it. The page of each message has the steps that fit it.

## If your script gets it

If a script of yours collects public pages and meets one of these, the system tells you what failed: the address, the client, a check that needs a browser, or a limit. Each guide explains its system, and one call to the Web Unlocker returns the page with the name of the system in the answer.

## Let the answer name the system

You do not have to read the block yourself. Send the URL to the REST endpoint: when the page comes back, `blocked` is `false`. When every attempt met a wall, the answer says which system it recognised in `vendor` and what kind of stop it was in `blockClass`.

cURL:

```bash
curl -X POST https://app.quanticdata.io/api/v1/scraper/unlock \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/", "country": "us"}'
```

Python:

```python
import requests

r = requests.post(
    "https://app.quanticdata.io/api/v1/scraper/unlock",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"url": "https://example.com/", "country": "us"},
    timeout=130,
)
page = r.json()["payload"]
print(page["status"], page["blocked"], page["latency_ms"], page["cost"])
print(page["body"][:500])
```

Node.js:

```javascript
const res = await fetch("https://app.quanticdata.io/api/v1/scraper/unlock", {
  method: "POST",
  headers: { Authorization: "Bearer YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({ url: "https://example.com/", country: "us" }),
});
const { payload: page } = await res.json();
console.log(page.status, page.blocked, page.latency_ms, page.cost);
console.log(page.body.slice(0, 500));
```

On the proxy endpoint the same two facts come back as the headers `x-qp-vendor` and `x-qp-block-class`.

### What the answer tells you

| Field | What it says |
| --- | --- |
| `blocked` | `false` when the real page came back. `true` only when every attempt met a block; the block page is then in `body`. |
| `vendor` | The system the engine recognised: `cloudflare`, `datadome`, `akamai`, `perimeterx`, `kasada`, `imperva`, `shape`, `awswaf`. A captcha widget is reported as `recaptcha` or `hcaptcha`, and anything else as `unknown`. |
| `blockClass` | The kind of stop. The values are in the next table. |
| `tier_served` | `tls` for a browser-grade request, `browser` when a real browser had to open the page. |
| `attempts`, `latency_ms` | How many tries the call took and how long it lasted. |

### The values of blockClass

| blockClass | What stopped the call |
| --- | --- |
| `js_challenge` | A check that a real browser clears by running a script. |
| `captcha` | The page asks a person: a puzzle, a slider, press and hold. |
| `access_denied` | A flat refusal, with no challenge offered. |
| `rate_limited` | A plain `429`: too many requests. |
| `fingerprint` | The client itself was judged automated. |
| `geo` | The site does not serve the country of the exit. |

The full list, with what to do for each value, is in the [Web Unlocker section of the API docs](https://quanticdata.io/docs/#tag/Web-Unlocker).

## How this dictionary was put together

Every row comes from the documentation of the system itself, listed at the foot of this page, and from the words the block pages print. Nothing here is taken from a forum.

The words and the marks are what each system sends by default. A site can restyle a block page, rename a cookie or change a status code, so treat one mark as a hint and two as an answer.

## Measured, with a date

The canary of 11 November 2026 runs a fixed list of 27 protected targets, sites of the eight systems in these tables among them: 72 of 81 calls came back with the real page, with a median response of 4.1 s.

A call counts only when the answer is 2xx and carries the real page, not a challenge. The list, the method and every run are on the [Web Unlocker status page](https://quanticdata.io/web-unlocker/status/).

## What it is for, and what it does not do

- It is for pages anyone can open in a browser without signing in: prices, listings, reviews, search results, public profiles.
- Challenges that need no human input are handled by the browser tier. An interactive captcha that asks a person to click, pick images or type is not solved: the answer comes back with `blocked: true` and `blockClass: "captcha"`, so your code can skip the page or try later.
- It does not log in for you and it does not create accounts. Pages behind a login stay behind it.
- Whether you may collect a page depends on the terms of the site and on the law that covers the data. A protection system does not change that, in either direction.

## Block pages: questions people ask

### What is a block page?

A block page is the answer a site's protection system sends in place of the page you asked for, when it judges a request automated or unwanted. It can be a refusal, a check that a browser clears by itself, a captcha, or an almost empty page with one script. Each system has its own wording.

### How do I tell which anti-bot system a site uses?

Read three things in the blocked answer: the words on the page, the status code, and the headers and cookies. The words are the most reliable, since each system prints its own sentence. The tables on this page map each of them to its system, and the Web Unlocker reports it in the vendor field.

### Why did I get a block page with status 200?

Because some systems serve their block as a normal answer. F5 BIG-IP sends its Request Rejected page with status 200 by default, and Imperva often does the same with its check. Code that trusts the status stores the block as data. Compare the body with what the page should contain.

### Is a 429 always a rate limit?

No. On a Cloudflare site with error 1015 it is: the address went over the limit the site set. On a Kasada site the 429 comes on the first request, with an almost empty page and a script, and has nothing to do with how fast you ask. A browser that runs the script gets the page.

### I am a visitor, not a scraper. Why do I see a block page?

Because these systems judge requests, and ordinary browsing can look unusual: a VPN or a shared address, a script blocker, cookies turned off, many tabs opened at once. Turn those off for the site and reload. If the page stays, send the site's support the reference or the ID that the page prints.

### What does the Web Unlocker return when a page is blocked?

The same JSON as for a page that came back, with blocked: true, the block page in body, the system it recognised in vendor and the kind of stop in blockClass, such as js_challenge, captcha, access_denied or rate_limited. Your code reads those fields instead of guessing from the status or the text.

## Send the URL that shows you a block page

Create the free account, open Web Unlocker in the dashboard and paste the URL into the test box. The answer shows the status, the tier that served the page, the attempts and the cost of the call.

[Start free](https://app.quanticdata.io/register?next=%2Funlock&utm_source=web-unlocker&utm_medium=website&utm_campaign=unlocker-guides&utm_content=block-pages-start-2) · [How the Web Unlocker works](https://quanticdata.io/web-unlocker/)

Each message:

- ["Please enable JS and disable any ad blocker"](https://quanticdata.io/web-unlocker/please-enable-js-and-disable-any-ad-blocker/)
- ["Access Denied ... on this server"](https://quanticdata.io/web-unlocker/access-denied-on-this-server/)
- [Error 1015](https://quanticdata.io/web-unlocker/cloudflare-error-1015/)
- [Error 1020](https://quanticdata.io/web-unlocker/cloudflare-error-1020/)
- ["Just a moment..."](https://quanticdata.io/web-unlocker/cloudflare-just-a-moment/)
- ["Pardon Our Interruption"](https://quanticdata.io/web-unlocker/pardon-our-interruption/)
- [Press and hold CAPTCHA](https://quanticdata.io/web-unlocker/press-and-hold-captcha/)
- ["The requested URL was rejected"](https://quanticdata.io/web-unlocker/request-rejected-support-id/)
- [Cloudflare Turnstile](https://quanticdata.io/web-unlocker/cloudflare-turnstile/)
- [CAPTCHA when scraping](https://quanticdata.io/web-unlocker/captcha-when-scraping/)

Each system:

- [Cloudflare](https://quanticdata.io/web-unlocker/bypass-cloudflare/)
- [DataDome](https://quanticdata.io/web-unlocker/bypass-datadome/)
- [Akamai Bot Manager](https://quanticdata.io/web-unlocker/bypass-akamai/)
- [PerimeterX (HUMAN)](https://quanticdata.io/web-unlocker/bypass-perimeterx/)
- [Kasada](https://quanticdata.io/web-unlocker/bypass-kasada/)
- [Imperva (Incapsula)](https://quanticdata.io/web-unlocker/bypass-imperva/)
- [F5 BIG-IP and Shape](https://quanticdata.io/web-unlocker/bypass-f5/)
- [AWS WAF](https://quanticdata.io/web-unlocker/bypass-aws-waf/)

Also:

- [Web Unlocker](https://quanticdata.io/web-unlocker/)
- [Status and canary](https://quanticdata.io/web-unlocker/status/)
- [Residential proxies](https://quanticdata.io/residential-proxies/)
- [Mobile proxies](https://quanticdata.io/mobile-proxies/)

## References

By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData · Published 11 November 2026 · Updated 11 November 2026 · [Read as Markdown](https://quanticdata.io/web-unlocker/block-pages/index.md)

- [Cloudflare docs: interstitial challenge pages](https://developers.cloudflare.com/cloudflare-challenges/challenge-types/challenge-pages/)
- [Cloudflare docs: detect a challenge page response (the cf-mitigated header)](https://developers.cloudflare.com/cloudflare-challenges/challenge-types/challenge-pages/detect-response/)
- [Cloudflare docs: 1xxx errors, with the status code of each](https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/)
- [Cloudflare docs: Turnstile widgets (managed, non-interactive and invisible modes, error states)](https://developers.cloudflare.com/turnstile/concepts/widget/)
- [DataDome docs: response pages (device check, captcha, block)](https://docs.datadome.co/docs/response-pages)
- [Akamai TechDocs: translate an error reference string](https://techdocs.akamai.com/edge-diagnostics/docs/translate-error-string)
- [HUMAN docs: the HUMAN Challenge (press and hold)](https://docs.humansecurity.com/applications/human-challenge)
- [Kasada: how its bot defense works (the product documentation needs a customer login)](https://www.kasada.io/bot-defense)
- [Imperva docs: Cloud WAF error pages and codes](https://docs-cybersec.thalesgroup.com/bundle/cloud-application-security/page/error-codes.htm)
- [Imperva docs: Advanced Bot Protection](https://docs-cybersec.thalesgroup.com/bundle/advanced-bot-protection/page/abp/94085.htm)
- [F5 knowledge base K92414462: the response and blocking pages of BIG-IP ASM](https://my.f5.com/manage/s/article/K92414462)
- [F5 TechDocs: configuring what happens if a request is blocked](https://techdocs.f5.com/en-us/bigip-17-0-0/big-ip-asm-implementations/configuring-what-happens-if-a-request-is-blocked.html)
- [AWS WAF developer guide: CAPTCHA and Challenge action behavior (status 405 and 202, the x-amzn-waf-action header)](https://docs.aws.amazon.com/waf/latest/developerguide/waf-captcha-and-challenge-actions.html)
- [Google reCAPTCHA docs: choosing the type of reCAPTCHA (v3, v2 checkbox, v2 invisible)](https://developers.google.com/recaptcha/docs/versions)
- [hCaptcha docs: how the widget and its token work](https://docs.hcaptcha.com/)
- [RFC 9110, section 15.5.4: 403 Forbidden](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.4)
- [RFC 6585, section 4: 429 Too Many Requests](https://www.rfc-editor.org/rfc/rfc6585.html#section-4)
- [Web Unlocker in the QuanticData API docs: request, answer, errors and how to read a block (vendor and blockClass)](https://quanticdata.io/docs/#tag/Web-Unlocker)
- [Web Unlocker status: the canary list, the method and every run](https://quanticdata.io/web-unlocker/status/)

---

Source: https://quanticdata.io/web-unlocker/block-pages/ · Site index for AI: https://quanticdata.io/llms.txt