THE FOMITE

Species index / toolkit

curl

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

1,168Requests
48Distinct IPs
77Well-known probes
2026-08-19First seen
2026-11-18Last seen

Identity

Kindagent
Familytoolkit
Stated purposeunknown
UA matchcurl/
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
/sitemap.xml1362026-08-192026-11-18
/llms.txt352026-08-192026-11-18
/.well-known/fomite.json182026-08-192026-08-22
/robots.txt122026-08-192026-10-29
/.well-known/oauth-authorization-server112026-08-282026-11-16
/openapi.json112026-08-192026-10-18
/.well-known/oauth-protected-resource102026-08-202026-10-14
/llms-full.txt82026-08-192026-09-21
/ai.txt72026-08-192026-08-24
/.well-known/security.txt62026-08-192026-08-24
/.well-known/oauth-protected-resource/mcp62026-08-202026-10-14
/.well-known/mcp.json62026-08-192026-08-25
/.well-known/mcp-manifest-attestation62026-08-222026-10-05
/.well-known/agent.json42026-08-192026-08-22
/.well-known/glama.json22026-08-192026-08-22
/.well-known/oauth-authorization-server/mcp22026-08-202026-08-20
/.well-known/ai-plugin.json22026-08-192026-08-22
/.well-known/openid-configuration12026-10-122026-10-12
/.well-known/openai-apps-challenge12026-11-172026-11-17

Protocol fingerprint

HTTPTLSCipherALPNRequests
HTTP/2.0TLS1.3TLS_AES_128_GCM_SHA256h21,291
HTTP/1.1TLS1.3TLS_AES_128_GCM_SHA256http/1.1709
HTTP/2.0TLS1.3TLS_CHACHA20_POLY1305_SHA256h242
HTTP/1.1------17
HTTP/1.1TLS1.3TLS_AES_128_GCM_SHA256--14
HTTP/2.0TLS1.2ECDHE-ECDSA-AES128-GCM-SHA256h21
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
t13d1312h2_a44d0ee8b3cc_e381dae6da6b67560f98d68783bd...13h2,http/1.1139
t13d3112h2_e8f1e7e78f70_b26ce05bbdd60149f47eabf9a20d...13h2,http/1.177
t13d2013h1_2b729b4bf6f3_e24568c0d440fae0e5d973c96ae1...13http/1.159
t13d4907h2_0d8feac7bc37_7395dae3b2f3375c6162a492dfbf...13h2,http/1.118
t13d3013h2_1d37bd780c83_8537cf56674e32e4b8812cda0c0d...13h2,http/1.110
t13d191000_9dc949149365_e7c2852226516f298f9c65263795...13--5

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

seen 5x

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

seen 2x

1. Host
2. User-Agent
3. Connection

seen 2x

Requests per day (60 days)

DayRequests 
2026-09-202
2026-09-211
2026-09-226
2026-09-236
2026-09-241
2026-09-253
2026-09-265
2026-09-277
2026-09-282
2026-09-293
2026-09-301
2026-10-013
2026-10-021
2026-10-031
2026-10-042
2026-10-057
2026-10-061
2026-10-071
2026-10-083
2026-10-091
2026-10-101
2026-10-111
2026-10-124
2026-10-131
2026-10-141
2026-10-151
2026-10-167
2026-10-179
2026-10-183
2026-10-191
2026-10-202
2026-10-211
2026-10-221
2026-10-233
2026-10-241
2026-10-259
2026-10-261
2026-10-273
2026-10-281
2026-10-296
2026-10-301
2026-10-311
2026-11-019
2026-11-022
2026-11-031
2026-11-041
2026-11-051
2026-11-061
2026-11-0713
2026-11-081
2026-11-091
2026-11-101
2026-11-112
2026-11-122
2026-11-131
2026-11-142
2026-11-153
2026-11-165
2026-11-172
2026-11-18788