// vendor intelligence
what castle detects
castle is a fraud-scoring vendor. it declares strong ip reputation (2/3), strong js fingerprint (2/3), strong behavioral (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 | 2/3 strong | asn, proxy-class, and abuse-history scoring of the connecting address. |
| js fingerprint | 2/3 strong | canvas, webgl, navigator, font, and audio signals collected in-page. |
| behavioral | 2/3 strong | mouse, keyboard, and timing biometrics read from interaction cadence. |
| challenge | unaddressed | interactive or invisible captcha and proof-of-work gates. |
| attestation | unaddressed | hardware or os-backed integrity checks (webauthn, play integrity, device attestation). |
| server coherence | unaddressed | 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
- cookies
- __cid
- endpoints
- d.castle.io, m.castle.io
- header tells
- castle.io, __cid, x-castle-request-token
- gate token
- castle request token (X-Castle-Request-Token)
account-abuse / login risk api: a client sdk mints a request token bound to device + behaviour, scored server-to-server (allow/challenge/deny) at auth-sensitive endpoints. identification + risk, not an edge gate.
questions
- what does castle detect?
- it declares strong ip reputation (2/3), strong js fingerprint (2/3), strong behavioral (2/3) capability. layers not listed are not enforced by castle.
- what are castle's tells?
- header/script tells: castle.io, __cid, x-castle-request-token. cookies: __cid. endpoints: d.castle.io, m.castle.io.
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.