ua-tracer by Paul Kinlan

recent traces · ua-tracer

ua-tracer

what does a user agent actually fetch, follow & run?

All recent homepage requests, newest first. This page does not mint a new trace (unlike /), so you can browse the log without adding noise.

Recent homepage requests

Filter by user agent and the matching requests appear right below. Showing requests whose user agent contains Go-http-client/2.0.

clear
TimestampUser AgentAssets
2026-11-08 16:46:54.176 UTC
Go-http-client/2.0
0
no JS—
2026-11-08 16:46:54.172 UTC
Go-http-client/2.0
0
no JS—
2026-10-26 21:42:47.760 UTC
Go-http-client/2.0
0
no JS—
2026-10-08 14:07:33.069 UTC
Go-http-client/2.0
0
no JS—
2026-09-22 08:44:45.077 UTC
Go-http-client/2.0
0
no JS—
2026-09-22 08:16:20.076 UTC
Go-http-client/2.0
0
no JS—
2026-09-13 14:57:09.958 UTC
Go-http-client/2.0
0
no JS—
2026-09-08 21:59:03.965 UTC
Go-http-client/2.0
0
no JS—
2026-08-23 18:01:21.504 UTC
Go-http-client/2.0
0
no JS—
2026-07-05 15:07:13.678 UTC
Go-http-client/2.0
0
no JS—
2026-07-03 05:03:19.651 UTC
Go-http-client/2.0
0
no JS—
2026-06-22 12:48:02.352 UTC
Go-http-client/2.0
0
no JS—
2026-06-22 12:08:09.098 UTC
Go-http-client/2.0
0
no JS—

By user agent

Running counts across all 28232 homepage requests (1 distinct agents). Click one to set the filter above.

User AgentRequestsJS ran
Go-http-client/2.0
13 0

Unsolicited / well-known requests

Paths a user agent fetched on its own that ua-tracer never links to: robots.txt, sitemap.xml, /.well-known/*, llms.txt, the root favicon, and similar. Reveals what an agent probes on its own initiative.

Filtered to user agent Go-http-client/2.0. clear filters

By path

Each unsolicited path with its request count and how many distinct user agents hit it. Click a path to see the individual requests; click a user agent below to reverse-look-up everything that UA did.

No unsolicited paths fetched yet.

Requests (0 shown)

The Related trace column links a probe to a homepage trace from the same user agent and IP within 30 minutes (the same crawler that fetched a well-known file usually also loaded /). The offset shows how long before/after the probe that trace was minted.

No unsolicited probe requests match the current filter.

← back to the live tracer (mints a new trace)