// vendor intelligence
what netacea detects
netacea is a behavioral vendor. it declares native behavioral (3/3), native server coherence (3/3), strong ip reputation (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 | unaddressed | canvas, webgl, navigator, font, and audio signals collected in-page. |
| behavioral | 3/3 native | 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 | 3/3 native | 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
- server-side log/edge ingestion (no client js injection)
- header tells
- server-side; no browser-visible sdk
server-side (agentless) bot management: ingests request logs / cdn traffic and scores intent from behaviour aggregates rather than a client sdk, so there is no js tell. the coherence is judged across the request stream.
questions
- what does netacea detect?
- it declares native behavioral (3/3), native server coherence (3/3), strong ip reputation (2/3) capability. layers not listed are not enforced by netacea.
- what are netacea's tells?
- header/script tells: server-side; no browser-visible sdk. endpoints: server-side log/edge ingestion (no client js injection).
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.