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 Bridgy Fed (https://fed.brid.gy/).

clear
TimestampUser AgentAssets
2026-07-02 18:55:30.675 UTC
Bridgy Fed (https://fed.brid.gy/)
0
no JS
2026-07-02 18:55:24.833 UTC
Bridgy Fed (https://fed.brid.gy/)
0
no JS
2026-07-02 18:55:22.545 UTC
Bridgy Fed (https://fed.brid.gy/)
0
no JS
2026-06-22 12:06:41.986 UTC
Bridgy Fed (https://fed.brid.gy/)
0
no JS
2026-06-22 12:06:40.604 UTC
Bridgy Fed (https://fed.brid.gy/)
0
no JS
2026-06-22 12:06:39.927 UTC
Bridgy Fed (https://fed.brid.gy/)
0
no JS

By user agent

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

User AgentRequestsJS ran
Bridgy Fed (https://fed.brid.gy/)
6 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 Bridgy Fed (https://fed.brid.gy/). 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)