Captcha demo: a live hCaptcha widget you can test.
Below is a real hCaptcha widget running on hCaptcha's official test sitekey. Tick the checkbox and the response token it hands back appears under it. After that, the page follows the token to the server: the siteverify call a site makes next, what the Enterprise test keys return, and how to get real tokens into a test pipeline.
10000000-ffff-ffff-ffff-000000000001
Loading the widget connects your browser to hCaptcha (js.hcaptcha.com),
which handles that request under its own privacy policy.
h-captcha-response What happened when you ticked the box
The demo loads api.js from js.hcaptcha.com and renders the
widget on 10000000-ffff-ffff-ffff-000000000001, the publisher test sitekey. hCaptcha scripts
that key: the checkbox passes on the first click, no puzzle opens, and the widget
returns the same dummy token every time,
10000000-aaaa-bbbb-cccc-000000000001.
On a normal form, hCaptcha writes that token into a hidden
h-captcha-response field, and the form sends it with everything else.
This demo has no form, so it reads the token from the widget's callback and prints
it. Here is the same setup in a few lines, if you want it on your own page:
// Page markup:
// <div id="captcha"></div>
// <script async defer
// src="https://js.hcaptcha.com/1/api.js?render=explicit&onload=onHcaptchaLoad"></script>
window.onHcaptchaLoad = () => {
hcaptcha.render('captcha', {
sitekey: '10000000-ffff-ffff-ffff-000000000001',
callback: (token) => {
// Same value hCaptcha writes into the hidden h-captcha-response field.
console.log('hCaptcha token:', token);
},
'expired-callback': () => {
// The token timed out before the form was sent; the visitor has to pass again.
},
});
};
A real sitekey works the same way in the browser, but the token is a long
P1_ string that changes on every pass and stops working after a short
time. The hCaptcha token guide covers that
format.
What a site does with the token next
A site accepts the token only after its server has checked it. The server posts it to
hCaptcha's siteverify endpoint together with its secret key, and lets the
request through only if the answer says success: true. For the test
sitekey the secret is the public all-zeros value:
curl "https://api.hcaptcha.com/siteverify" \
-d "secret=0x0000000000000000000000000000000000000000" \
-d "response=10000000-aaaa-bbbb-cccc-000000000001" {
"success": true,
"credit": false,
"hostname": "dummy-key-pass",
"challenge_ts": "2026-11-01T19:02:29.372Z"
}
Two things in that response give the test away. hostname is
dummy-key-pass rather than the domain the widget ran on, and the token
is never used up: we sent the same dummy token several times in a row and every call
returned success: true. A real token passes siteverify once. A second
call with the same string fails, so code that retries a verification will behave
differently in production than it did against the test key.
Every parameter and response field, with server code in four languages, is in the siteverify guide. If a call fails, hCaptcha error codes lists what each code means.
The Enterprise test key sets
Enterprise accounts get two more test sitekeys. Both widgets behave exactly like the demo above, and both dummy tokens verify against the same all-zeros secret. What differs is the risk verdict siteverify attaches, which lets you exercise the branch of your code that handles a suspected bot:
| Test sitekey | Dummy token | siteverify with remoteip |
|---|---|---|
20000000-ffff-ffff-ffff-000000000002 | 20000000-aaaa-bbbb-cccc-000000000002 | score: 0, score_reason: ["safe"] |
30000000-ffff-ffff-ffff-000000000003 | 30000000-aaaa-bbbb-cccc-000000000003 | score: 1, score_reason: ["bot"] |
The score only shows up when the request includes remoteip. Without it,
both tokens came back with success: true and no score field
at all, so a test that checks the score has to send an IP:
curl "https://api.hcaptcha.com/siteverify" \
-d "secret=0x0000000000000000000000000000000000000000" \
-d "response=30000000-aaaa-bbbb-cccc-000000000003" \
-d "remoteip=203.0.113.7" {
"success": true,
"hostname": "dummy-key-pass",
"sitekey": "30000000-ffff-ffff-ffff-000000000003",
"challenge_ts": "2026-11-01T19:02:58.702Z",
"score": 1,
"score_reason": ["bot"],
"scoped_uid_0": "C0_…"
}
The full table of test keys, and the not-using-dummy-secret error you
hit when you mix test and real values, are on
the hCaptcha test sitekey page.
Real tokens for automated tests
The test keys check your wiring: that the form posts the field and your server calls siteverify. They can't show how the form behaves on your real sitekey, where a token expires and works only once, and a visitor may get a challenge first. Testing that in staging takes real tokens, and a CI run can't stop for someone to click through images.
With the NoneCap hCaptcha solver, your test sends the sitekey and
page URL of your staging form to POST /v1/solves and gets back a real
P1_ token for that key, which it submits as
h-captcha-response. Your server verifies it with your real secret, the
same as for a visitor.
curl "https://api.nonecap.com/v1/solves?wait=90" \
-H "Authorization: Bearer $NONECAP_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "hcaptcha",
"sitekey": "f5ab1c2d-7e8f-4a9b-b1c2-d3e4f5a6b7c8",
"url": "https://staging.your-site.example/signup"
}' Request and response fields, errors and the SDKs are in the API reference. What a solve costs is on the pricing page, and new accounts get free credits to try it.
Last updated November 2026.
Frequently asked
Where can I try an hCaptcha demo?
Why did the demo not show me an image challenge?
What is the token in the hCaptcha demo?
10000000-aaaa-bbbb-cccc-000000000001, the fixed dummy token for the publisher test sitekey. A real widget on a real sitekey returns a long P1_ string instead; the hCaptcha token guide explains its format and lifetime.The demo widget does not load. Why?
js.hcaptcha.com blocked the script: usually an ad or tracker blocker, Brave Shields, or a strict network filter. Allow hCaptcha on this page and press the button again. hCaptcha not working walks through each case.