Bot management · Radware (ShieldSquare)
Radware Bot Manager
Difficulty 4/5
The former ShieldSquare engine. Intent-based scoring, most visible through its `validate.perfdrive.com` interstitial.
- TLS fingerprinting
- JS challenge required
- Behavioural scoring
- IP reputation weight: high
How it decides
-
Device and browser fingerprinting joined to a per-visitor intent score.
-
A redirect to `validate.perfdrive.com` for anything it wants to re-check.
-
Crowd-sourced bot intelligence shared across its customer base.
What you see when it stops you
- A redirect to `validate.perfdrive.com`
- `_rdblts` cookies or `x-sl-compstate` headers
- HTTP 403 at the end of a redirect chain
Signatures the detector matches
Publicly observable artefacts Radware Bot Manager sends to every visitor. Paste a response into the analyser and these are what it looks for.
| Where | Signal | Weight |
|---|---|---|
| Page markup | validate.perfdrive.com interstitial | 75 |
| Header | x-sl-compstate header | 60 |
| Cookie | _rdblts cookie | 55 |
What actually gets through
-
Residential exits and a real browser.
-
Follow the validation redirect properly and keep the resulting cookies — clients that drop the chain are trivially flagged.
Not sure this is what
is blocking you?
Paste the response you actually got. The detector names the vendor from its own headers, cookies and challenge markup — no account, nothing uploaded.