Reachable By

Last updated October 21, 2026

Our scanner

Who we are

Reachable By checks websites for accessibility problems — things like buttons a screen reader can't name or text too faint to read. Our scanner visits only pages that a Reachable By customer added to their own account: usually their own site, or a client's site they look after.

How to recognize it

It's a normal Chrome browser, and its User-Agent ends with:

(compatible; ReachableBy/1.0; +https://reachableby.com/bot)

What it does on your site

  • Loads one page the way a visitor would, waits for it to finish, and checks it against WCAG 2.2 AA.
  • Never fills in forms, logs in, buys anything or follows links around your site.
  • On paid plans it comes back about once a week per page; otherwise only when the customer asks.
  • If a page refuses us, we try again at most once a day — we don't hammer it.

Why a check might be blocked

Bot protection (Cloudflare, DataDome and similar) is built to stop automated traffic, and an accessibility check is automated. We don't try to sneak past it — we'd rather you decide. If you run the site and want the checks, add one of the rules below. If you didn't ask for them, there's nothing to do: a blocked check simply doesn't happen.

Let our scanner through

Cloudflare

  1. Go to Security → WAF → Custom rules (in the newer dashboard: Security rules) and create a rule.
  2. Field User Agent, operator contains, value ReachableBy.
  3. Action Skip, and tick All Super Bot Fight Mode rules and any managed rules that challenge visitors. Deploy.
  4. On the Free plan, the basic Bot Fight Mode can't be skipped for a single tool — Cloudflare only lets you switch it off (Security → Bots). If you'd rather keep it on, the check will stay blocked.

DataDome

  1. In the DataDome dashboard, open Custom rules and add a rule.
  2. Condition: User-Agent contains ReachableBy. Response: Allow.
  3. Save — it takes effect within a few minutes.

Akamai

  1. In Bot Manager, define a custom bot matched by User-Agent containing ReachableBy.
  2. Set its action to Allow in your security policy and activate the configuration.

Imperva

  1. Under Security → Policies, add a custom rule where the User-Agent contains ReachableBy.
  2. Set the action to Allow / Bypass for bot protection.

Sucuri

  1. Sucuri allowlists by IP address rather than User-Agent. Add our address ranges under Firewall → Access Control → Allowlist IP.

Something else

Ask your hosting provider or web team to allow requests whose User-Agent contains ReachableBy.

Allowing by IP address

If your firewall only works with IP addresses, our checks come from these ranges:

  • 74.220.50.0/24
  • 74.220.58.0/24

These ranges belong to our hosting provider and are shared with other services hosted there, so allowing them lets more than just our scanner through. Prefer the User-Agent rule where you can. Questions: hello@reachableby.com.

Then run the check again from Reachable By — the weekly re-scan will pick it up on its own within a day.