The classic Amazon CAPTCHA is the "Enter the characters you see below" page Amazon shows when its risk engine thinks a browser is automated. It is a distorted-text image, not the AWS WAF challenge: those are two separate products on different pages. OCR handles it easily, but passing it does not on its own repair a session Amazon has flagged.
How to identifyLink to How to identify
- An "Amazon.com" title and the prompt "Enter the characters you see below"
- A form posting to
/errors/validateCaptchawith methodGET - Hidden fields
amznandamzn-r - The answer box
field-keywords - An image from
images-na.ssl-images-amazon.com/captcha/... - A "Try different image" link and a "Continue shopping" button
- The footer line "Sorry, we just need to make sure you're not a robot"
How it worksLink to How it works
- When a session looks suspicious, Amazon's risk engine redirects it to this page.
- The page carries hidden tokens (
amzn,amzn-r) alongside the text image. - The visitor types the characters into
field-keywordsand sends the form. - Amazon checks the answer and the hidden tokens, then redirects back to the original path.
- Case usually doesn't matter, but every wrong answer pushes the risk score up.
- Passing resets the session's risk score for the moment. It does not earn lasting trust.
Amazon CAPTCHA vs AWS WAFLink to Amazon CAPTCHA vs AWS WAF
- Amazon CAPTCHA: the old-style text image on
amazon.com/errors/validateCaptcha. - AWS WAF CAPTCHA: a different AWS product with its own widget, puzzle and token. See Amazon WAF.
Free & open-source bypass methodsLink to Free & open-source bypass methods
| Tool | What it does | Success Rate | Link |
|---|---|---|---|
| ddddocr | Reads Amazon's fairly clean text images very well | 90–98% | sml2h3/ddddocr |
| Tesseract + preprocessing | Thresholding, deskewing and an alphanumeric whitelist | 70–90% | tesseract-ocr/tesseract |
| EasyOCR | A sturdy default when images are noisy | 80–95% | JaidedAI/EasyOCR |
| Playwright / DrissionPage | Keeps the session, sends the form and follows the redirect | 90–98% | microsoft/playwright-python · g1879/DrissionPage |
Practical approachLink to Practical approach
- Stay in the browser session that got the CAPTCHA. Don't open a new one.
- Download the image and clean it: grayscale, more contrast, threshold.
- Read it with ddddocr or Tesseract, removing spaces and punctuation.
- Fill in
field-keywordsand submit with the originalamznandamzn-rvalues. - Follow the redirect and confirm the product page actually loads.
- If the CAPTCHA keeps coming back, slow down and switch to a cleaner IP rather than retrying fast.
Practical tipsLink to Practical tips
- Amazon generally ignores case, but submit the characters exactly as OCR read them.
- The hidden
amznandamzn-rfields link your answer to the original request. Keep them intact. - A solved CAPTCHA won't make up for a poor IP or a robotic request rhythm.
- For everyday browsing, skip incognito and fresh profiles. A signed-in account earns more trust.
- Mobile pages lay the same CAPTCHA out differently. Recognise it by the form action rather than its look.
- Don't mistake this page for the AWS WAF challenge, which needs a different approach.