Can PluginView detect Google reCAPTCHA without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Google reCAPTCHA — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Google reCAPTCHA?

Google reCAPTCHA is classified under Consent, CAPTCHA & Accessibility in the PluginView directory.

How many fingerprint rules cover Google reCAPTCHA?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Google reCAPTCHA?

Illustrative public indicators for Google reCAPTCHA include www.google.com/recaptcha; www.gstatic.com/recaptcha. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Google reCAPTCHA?

For Google reCAPTCHA, start with: Forms, signup, checkout.

Detect Google reCAPTCHA

Consent, CAPTCHA & Accessibility

PluginView detects Google reCAPTCHA, a Consent, CAPTCHA & Accessibility, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Google reCAPTCHA include www.google.com/recaptcha, www.gstatic.com/recaptcha. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Google reCAPTCHA

Loading website list…

Signal classes

PluginView evaluates public page signals in these classes when identifying Google reCAPTCHA. Individual fingerprint rule bodies are proprietary and are not published.

Vendor endpoints

Example public indicators for Google reCAPTCHA

Illustrative indicators derived from public catalog metadata for Google reCAPTCHA. A live scan may match additional proprietary rules beyond these examples.

www.google.com/recaptcha
www.gstatic.com/recaptcha

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: Forms, signup, checkout

How to check a site for Google reCAPTCHA

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Google reCAPTCHA signals (prefer: Forms, signup, checkout).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Google reCAPTCHA signature set (2 rules).
3. Review the confidence score and text explanation for Google reCAPTCHA on the results page.

FAQ: detecting Google reCAPTCHA

Can PluginView detect Google reCAPTCHA without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Google reCAPTCHA — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Google reCAPTCHA?: Google reCAPTCHA is classified under Consent, CAPTCHA & Accessibility in the PluginView directory.
How many fingerprint rules cover Google reCAPTCHA?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Google reCAPTCHA?: Illustrative public indicators for Google reCAPTCHA include www.google.com/recaptcha; www.gstatic.com/recaptcha. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Google reCAPTCHA?: For Google reCAPTCHA, start with: Forms, signup, checkout.