Detect AudioEye
AudioEye is an accessibility overlay which claims to provide ADA and WCAG accessibility compliance.
01
Websites using AudioEye
55 hostnames in the PluginView corpus for this technology.
| Hostname | Last seen |
|---|---|
| hostgator.com | 8/3/2026 |
| typepad.com | 8/3/2026 |
| horizon.com | 8/3/2026 |
| domain.com | 8/3/2026 |
| ipage.com | 8/3/2026 |
Whole list · $5.50 (55 × $0.10)
Sign in to purchase02
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.
03
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: All public pages
04
How to check a site for AudioEye
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest AudioEye signals (prefer: All public pages).
- 2. PluginView reads only public responses and scores them against proprietary AudioEye fingerprints. Rule bodies and identifiers are not published.
- 3. Review the confidence score and text explanation for AudioEye on the results page.
05
FAQ: detecting AudioEye
- Can PluginView detect AudioEye without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for AudioEye. It does not bypass authentication or paywalls.
- What category is AudioEye?
- AudioEye is classified under Accessibility, Consent, CAPTCHA & Accessibility in the PluginView directory.
- Does PluginView publish AudioEye fingerprint rules?
- No. Detection uses proprietary fingerprint rules that are not published. Scan results explain matches in plain language without disclosing rule bodies or identifiers.
- Which pages are best for detecting AudioEye?
- For AudioEye, start with: All public pages.
