THE FOMITE

Species index / toolkit

curl

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

286Requests
5Distinct IPs
48Well-known probes
2026-08-19First seen
2026-10-04Last seen

Identity

Kindagent
Familytoolkit
Stated purposeunknown
UA matchcurl/
Verifiedno
robots.txtignores

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
/sitemap.xml722026-08-192026-10-03
/llms.txt332026-08-192026-09-27
/.well-known/fomite.json182026-08-192026-08-22
/robots.txt92026-08-192026-09-29
/llms-full.txt82026-08-192026-09-21
/openapi.json82026-08-192026-09-01
/.well-known/oauth-authorization-server72026-08-282026-10-01
/ai.txt72026-08-192026-08-24
/.well-known/oauth-protected-resource72026-08-202026-09-28
/.well-known/mcp.json62026-08-192026-08-25
/.well-known/security.txt62026-08-192026-08-24
/.well-known/mcp-manifest-attestation52026-08-222026-09-15
/.well-known/agent.json42026-08-192026-08-22
/.well-known/oauth-protected-resource/mcp32026-08-202026-08-28
/.well-known/oauth-authorization-server/mcp22026-08-202026-08-20
/.well-known/glama.json22026-08-192026-08-22
/.well-known/ai-plugin.json22026-08-192026-08-22

Protocol fingerprint

HTTPTLSCipherALPNRequests
HTTP/1.1TLS1.3TLS_AES_128_GCM_SHA256http/1.1757
HTTP/2.0TLS1.3TLS_AES_128_GCM_SHA256h2359
HTTP/2.0TLS1.3TLS_CHACHA20_POLY1305_SHA256h222
HTTP/1.1------16
HTTP/1.1TLS1.3TLS_AES_128_GCM_SHA256--10
HTTP/2.0TLS1.2ECDHE-ECDSA-AES128-GCM-SHA256h22
HTTP/1.1TLS1.2ECDHE-ECDSA-CHACHA20-POLY1305--1

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
t13d3112h2_e8f1e7e78f70_b26ce05bbdd60149f47eabf9a20d...13h2,http/1.159
t13d2013h1_2b729b4bf6f3_e24568c0d440fae0e5d973c96ae1...13http/1.156
t13d4907h2_0d8feac7bc37_7395dae3b2f3375c6162a492dfbf...13h2,http/1.112
t13d3013h2_1d37bd780c83_8537cf56674e32e4b8812cda0c0d...13h2,http/1.110
t13d9013h2_c6771aded2ed_57a60bdf03d1c654189f0cbcfb63...13h2,http/1.13
t13d3013h2_1d37bd780c83_8537cf56674e7a73fb0bdeaa2a79...13h2,http/1.13

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. Host
2. User-Agent
3. Accept

seen 6x

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

seen 3x

1. User-Agent
2. Host
3. Accept

seen 3x

1. Host
2. User-Agent
3. Connection

seen 2x

Requests per day (60 days)

DayRequests 
2026-08-1973
2026-08-203
2026-08-211
2026-08-2211
2026-08-239
2026-08-244
2026-08-252
2026-08-261
2026-08-271
2026-08-281
2026-08-2912
2026-08-302
2026-08-311
2026-09-012
2026-09-021
2026-09-031
2026-09-041
2026-09-051
2026-09-061
2026-09-071
2026-09-081
2026-09-091
2026-09-101
2026-09-111
2026-09-121
2026-09-136
2026-09-141
2026-09-1518
2026-09-1644
2026-09-171
2026-09-181
2026-09-1911
2026-09-202
2026-09-211
2026-09-226
2026-09-236
2026-09-241
2026-09-253
2026-09-265
2026-09-278
2026-09-288
2026-09-296
2026-09-3013
2026-10-015
2026-10-022
2026-10-034