// vendor intelligence
what f5 shape detects
f5 shape is a behavioral vendor. it declares native js fingerprint (3/3), native attestation (3/3), strong behavioral (2/3), strong challenge (2/3), strong server coherence (2/3) capability. below: the layers it enforces and the cookie, endpoint, and header tells it leaves.
enforced detection layers
| detection layer | capability | what it covers |
|---|---|---|
| tls / network fingerprint | unaddressed | the ja3/ja4 clienthello and http/2 settings signature the edge reads before any javascript runs. |
| ip reputation | unaddressed | asn, proxy-class, and abuse-history scoring of the connecting address. |
| js fingerprint | 3/3 native | canvas, webgl, navigator, font, and audio signals collected in-page. |
| behavioral | 2/3 strong | mouse, keyboard, and timing biometrics read from interaction cadence. |
| challenge | 2/3 strong | interactive or invisible captcha and proof-of-work gates. |
| attestation | 3/3 native | hardware or os-backed integrity checks (webauthn, play integrity, device attestation). |
| server coherence | 2/3 strong | cross-checking headers, tls, ip, and js for internal consistency. |
unaddressed means this tool type does not operate at that layer, so it is not a failing score. a red 0/3 is a real, declared score of zero. both are declared capability, not live pass-rates.
tells
- endpoints
- customer-proxied collector behind the origin domain
- header tells
- $rsc=
obfuscated js vm runs proprietary bytecode; encrypted signal blob -> short-lived rotating token (minute cadence), silent fail. f5 acquired shape 2020.
questions
- what does f5 shape detect?
- it declares native js fingerprint (3/3), native attestation (3/3), strong behavioral (2/3), strong challenge (2/3), strong server coherence (2/3) capability. layers not listed are not enforced by f5 shape.
- what are f5 shape's tells?
- header/script tells: $rsc=. endpoints: customer-proxied collector behind the origin domain.
sites defended by this vendor
other vendors
where to go from here
layer intensities are catalog-declared (0..3), speculative, and the catalog carries no capture date for this record. layer definitions in the glossary.