Details below are from the CAPTCHA services’, Google’s and Apple’s documentation on 13 November 2026. Check them for current details.
CAPTCHA test keys
Use these in development and staging only, read from environment variables so production keeps its real keys.
Cloudflare Turnstile has site keys for each outcome and secret keys that pass or fail on the server:
| Site key | Behaviour |
|---|---|
1x00000000000000000000AA |
Always passes, visible |
2x00000000000000000000AB |
Always blocks, visible |
1x00000000000000000000BB |
Always passes, invisible |
2x00000000000000000000BB |
Always blocks, invisible |
3x00000000000000000000FF |
Forces an interactive challenge |
| Secret key | Behaviour |
|---|---|
1x0000000000000000000000000000000AA |
Always passes |
2x0000000000000000000000000000000AA |
Always fails |
3x0000000000000000000000000000000AA |
Fails as “token already spent” |
The test site keys return the token XXXX.DUMMY.TOKEN.XXXX, which production secret keys refuse.
hCaptcha and Google reCAPTCHA v2 each have one pair that passes every check:
| Key | What it is |
|---|---|
10000000-ffff-ffff-ffff-000000000001 |
hCaptcha site key |
0x0000000000000000000000000000000000000000 |
hCaptcha secret key |
6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI |
reCAPTCHA v2 site key |
6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe |
reCAPTCHA v2 secret key |
reCAPTCHA’s test widget shows a warning that it’s for testing. reCAPTCHA v3 has no test keys: create a separate key for your test environments.
Test the failure too. With Turnstile’s blocking keys, check that the form says what went wrong and lets the person try again, rather than failing silently.
Google sign-in
Google may block sign-ins from browsers that are controlled by automation software, so an end-to-end test that types into Google’s sign-in page is fragile at best. Test the parts that are yours:
- The callback. Call your sign-in callback with a token from a test you control (many auth libraries and providers have a test mode or a way to mint a session for a test user), and check the user is created and signed in.
- The account rules. A Google sign-in with an address that already has a password account links to it, or is refused with a clear message, whichever you chose.
- The first-run screens. What a new Google user sees after sign-in: terms, a username, a profile step.
- One check by hand. Before a release, sign in with Google once yourself, on staging.
Sign in with Apple
Apple publishes no sandbox for Sign in with Apple, so test it the same way: the callback and account rules automatically, and one sign-in by hand with a real Apple Account before a release.
One thing to test on purpose: people can hide their email. Apple then gives your app a relay address at privaterelay.appleid.com, and your emails reach the person only if you’ve registered your sending domains or addresses with Apple. Check that your app accepts that address in its own validation, and that your confirmation and receipt emails are sent from a registered sender.
Where Proxy Mail QA fits
Most sign-up forms offer email as well as Google and Apple. Test that path with a new Proxy Mail QA address each run, through the CAPTCHA’s test keys, and check the confirmation email arrives and works.