THE FOMITE

Species index / toolkit

OkHttp

Operator not identifiable from the User-Agent alone. Identity is self-declared and unverified.

34Requests
2Distinct IPs
5Well-known probes
2026-08-19First seen
2026-11-14Last seen

Identity

Kindagent
Familytoolkit
Stated purposeunknown
UA matchokhttp
Verifiedno
robots.txtcompliant

What it went looking for

The order and selection of discovery paths is a design fingerprint: it reflects which conventions whoever built this client decided to support.

PathHitsFirstLast
/robots.txt32026-10-012026-10-29
/sitemap.xml22026-09-302026-09-30

Protocol fingerprint

HTTPTLSCipherALPNRequests
HTTP/2.0TLS1.3TLS_AES_128_GCM_SHA256h242
HTTP/1.1TLS1.3TLS_AES_128_GCM_SHA256--2
HTTP/1.1------2

TLS client fingerprint

Captured off the wire before the proxy terminates TLS. JA4 is stable across IP changes and much harder to spoof than a User-Agent string, so it is the strongest identity signal on this page.

JA4JA3TLSALPNSeen
t13d1114h2_5e2a75874763_89e9e4bb34190a80f68631b6e8b4...13h2,http/1.113
t13d1312h2_a44d0ee8b3cc_e381dae6da6b67560f98d68783bd...13h2,http/1.13
t13d311000_e8f1e7e78f70_e1d1bdc3e2a25cc600468c246704...13--2

Header order

The order a client sends its HTTP headers in is a design fingerprint of the library that built the request. Captured on plaintext port 80 only, since the proxy normalises order before the application sees it.

1. Accept
2. Accept-Language
3. User-Agent
4. Accept-Encoding
5. Host

seen 2x

Requests per day (60 days)

DayRequests 
2026-09-302
2026-10-012
2026-10-291
2026-11-051
2026-11-141