---
title: "CAPTCHA, Google and Apple sign-in in automated tests · Proxy Mail QA"
description: "Test keys for reCAPTCHA, hCaptcha and Turnstile, and how to test sign-up when Google or Apple sign-in can't be automated. For development and staging only."
url: https://proxymail.qa/solve/captcha-and-social-sign-in-tests
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# CAPTCHA, Google and Apple sign-in in automated tests

A CAPTCHA is there to stop scripts, and your end-to-end test is a script. Google and Apple sign-in are built the same way. The answer isn't to defeat them: each CAPTCHA service publishes test keys for development, and social sign-in is tested around the provider, not through it.

Updated 13 November 2026

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.

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-captcha-and-social-sign-in-te)

## Questions

### Can Proxy Mail QA solve CAPTCHAs?

No, and neither Proxy Mail QA for Chrome nor the agent tools ever fill one. Use the CAPTCHA service's test keys in development and staging, so the widget always passes there.

### Is it safe to ship the test keys?

No. They pass every request, so production with a test key has no CAPTCHA at all. Read the keys from environment variables, and add a release check that production's site key isn't one of the test keys.

### Does reCAPTCHA v3 have test keys?

No. Google's advice is to create a separate key for your testing environments.

### Why can't my test sign in with Google?

Google may block sign-ins from browsers controlled by automation software. Test your app's side of the sign-in instead, as below, and keep one check by hand before a release.

## Related guides

- [Test sign-up and email verification](https://proxymail.qa/solve/email-verification-testing): A fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.
- [Test OTP and one-time login codes](https://proxymail.qa/solve/otp-code-testing): Codes pulled out of the email with a Copy button and a countdown when the email says how long they last.
- [Test magic links and passwordless sign-in](https://proxymail.qa/solve/magic-link-testing): Single-use links that are never opened or prefetched on our side, so they still work when you click them.
- [Test password reset emails](https://proxymail.qa/solve/password-reset-testing): Request, receive and use reset links, and keep the new password saved next to the test account.
- [Stop sharing one Gmail inbox for QA](https://proxymail.qa/solve/shared-test-inbox): Private, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.
- [Stop using Gmail for test codes](https://proxymail.qa/solve/gmail-test-inbox): Why reading codes from Gmail over its API or IMAP keeps breaking your tests, and how one address per test removes the inbox from the problem.
- [Email limits in auth providers while you test](https://proxymail.qa/solve/auth-email-limits): Supabase's 2 an hour, Firebase's 5 email links a day, Auth0's 10 a minute and Clerk's 100 a month, and how to send your own.
- [Let test addresses through a disposable-email block](https://proxymail.qa/solve/disposable-email-blocks): Keep the block for real users and let your test domains through in development and staging, with one setting you can't ship by mistake.
- [Take QA notes by voice with Wispr Flow](https://proxymail.qa/solve/voice-notes-wispr-flow): Dictate what each test account is for, its state and what you found, straight into its notes, in seconds.
- [Test phone-first sign-up without real SMS](https://proxymail.qa/solve/phone-first-sign-up-testing): Test numbers with fixed codes, a test-mode code kept out of release builds, and why virtual numbers usually fail.
- [Test sign-up for people in China](https://proxymail.qa/solve/china-sign-up-testing): Real-name rules, a 姓名 field and province menus, a safe test code, and 身份证 numbers that can't be anyone's.
- [Test sign-up for people in Japan](https://proxymail.qa/solve/japan-sign-up-testing): Furigana fields, 全角 and 半角, postcode lookups and LINE sign-in, with test accounts that have Japanese names.
- [Made-up test accounts, not masked production data](https://proxymail.qa/solve/synthetic-test-data): A masked copy of production still holds real people. Test sign-up with made-up accounts that no one owns instead.
- [Test sign-up for people in India](https://proxymail.qa/solve/india-sign-up-testing): Test accounts with one name, PIN codes that agree with the city, phone-first sign-up, Hindi labels, ID fields and card mandates.
- [Test sign-up for people in Pakistan](https://proxymail.qa/solve/pakistan-sign-up-testing): Test accounts with Pakistani names in both scripts, CNIC fields that never hold a real number, and phone-first sign-up.
- [Fill phone and ID fields safely](https://proxymail.qa/solve/phone-id-and-tax-number-fields): Numbers set aside for fiction, your app's own test numbers, ID values that never match a real person, and KYC sandbox values, filled the same way by agents and tests.
- [Verification link points to localhost:3000](https://proxymail.qa/solve/localhost-links): Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.
- [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): Emails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.
- [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): Missing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.
- [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): The login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.
- [Check that one user can't see another's data](https://proxymail.qa/solve/vibe-coded-app-data-leaks): A curl with the anon key for tables anyone can read, and two signed-up accounts for policies that let every user read every row.
- [Triage sign-up and login bug reports with an agent](https://proxymail.qa/solve/bug-report-triage): An agent signs up with a new test address, watches the inbox, and answers replicated, not replicated or inconclusive, with the evidence.
- [A self-improvement loop for agents that build sign-up](https://proxymail.qa/solve/agent-self-improvement-loop): The agent builds, signs up with a test address, reads what the email did, fixes its own work and runs again. Proxy Mail QA is the tool it checks with.
- [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests): A complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.
- [Test sign-ups over several screens](https://proxymail.qa/solve/multi-step-sign-up-testing): One test account across every screen of the sign-up, with your form's own questions filled the same way each time.
- [Test sign-up emails in Cypress](https://proxymail.qa/solve/cypress-email-tests): A complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.
- [Test sign-up emails with pytest](https://proxymail.qa/solve/pytest-email-tests): A complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.
- [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing): The coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.
- [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing): The unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.
- [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse): Versions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.
- [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): Let an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.
- [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): An agent tries every field with values made for it, then finishes the registration through the email.
- [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): A checklist for your browser and phone, in the order that finds the most problems.
- [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): 12 checks for a form with an email, a password and perhaps a name.
- [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): One test account across every screen, and the verification email wherever it comes.
- [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): The emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.
- [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): A new, real address for every registration try, with the code or link ready to use.
- [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): Test accounts with saved passwords and an inbox for codes, magic links and resets.
- [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST's numbers for password length and rules, and test passwords to check yours.
- [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): The eight usual causes of a silent password field, and how to tell which one it is.
- [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): A whole-site check in an afternoon, in the order that finds the costliest problems first.
- [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): A toolkit by area, most of it free and none of it ours, except for account emails.
- [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): The full list, then which parts a simple site can skip.

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)
