Browser and connection check (TLS fingerprinting)
Many scrapers send a web browser's user agent, such as Chrome's, so that they look like a visitor. The way they open an HTTPS connection usually gives them away: every browser family offers its encryption options (ciphers) in its own order, and a script built on a common library offers them in a different one.
Browser and connection don't match is a Captcha Protection check for page visits whose user agent says it's a web browser but whose HTTPS connection doesn't look like that browser.
It never blocks
A mismatch on its own never blocks anyone. The visitor is asked to complete the browser check, which people pass in a few seconds, and they then keep browsing without another check. Only page visits are checked: requests for data (such as an API or a form answering with JSON) are never checked for this, so apps and site features keep working.
What it compares
| User agent says | Connection must look like | Otherwise |
|---|---|---|
| Chrome, Edge, Opera, Samsung Internet or another Chromium browser, Safari, or any browser on iPhone and iPad | Chromium or Safari | Browser check |
| Firefox | Firefox | Browser check |
| Anything else (search engines, monitoring tools, apps, scripts that say who they are) | Not compared | Not checked by this |
Plain HTTP requests aren't compared, and the check only works on domains whose HTTPS the sentry handles (Website protection with HTTPS on). Verified Identified traffic, your never-check addresses, your own sentries, origin servers and cluster VIP, your SSH allow-list, certificate checks, payment gateway notifications and visitors who already passed the check are never checked.
Turning it on
On Settings › Captcha Protection, choose Browser and connection don't match:
| Choice | What happens |
|---|---|
| Off | Not checked (the default) |
| Log only (record who would be checked) | Nobody is checked. Logs shows who would have been, as Browser check: browser and connection don't match under Would have blocked, last 24 hours on the domain's Blocks tab |
| On (check visitors) | Mismatched page visits are asked to complete the browser check |
Start with Log only. Some company networks inspect HTTPS traffic and connect on their staff's behalf, so their staff can be asked to complete the check too. Look at Logs before you turn it on.
On the All clusters tab, the choice applies to every cluster. A cluster tab can only choose a stronger setting for that cluster. While a domain's Website protection rules are in log mode, the check only logs.
Domain owners
Domain owners can't turn this check on, but when you let them change Captcha Protection (see Owner access) they can turn it off for their domain by ticking Turn off the browser and connection check for my domain on the owner area's Settings tab. If you take the permission away, their choice is paused and the check applies again.
In your logs
Visitors who got the check show on Logs as Browser check: browser and connection don't match. The domain's Captcha Protection card lists Browser and connection don't match (or Browser and connection don't match (log only)) among its checks.
This check needs sentry release 1.1 or later: older sentries ignore it.