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 SummalyBot/5.1.0.

clear
TimestampUser AgentAssets
2026-07-26 17:28:45.358 UTC
SummalyBot/5.1.0
0
no JS
2026-07-26 17:28:43.208 UTC
SummalyBot/5.1.0
0
no JS
2026-07-23 20:27:54.045 UTC
SummalyBot/5.1.0
0
no JS
2026-07-23 20:27:51.703 UTC
SummalyBot/5.1.0
0
no JS
2026-07-20 09:43:30.047 UTC
SummalyBot/5.1.0
0
no JS
2026-07-20 09:43:27.921 UTC
SummalyBot/5.1.0
0
no JS
2026-07-12 09:07:18.258 UTC
SummalyBot/5.1.0
0
no JS
2026-07-12 09:07:16.536 UTC
SummalyBot/5.1.0
0
no JS
2026-07-10 17:43:23.958 UTC
SummalyBot/5.1.0
0
no JS
2026-07-10 17:43:22.111 UTC
SummalyBot/5.1.0
0
no JS
2026-07-09 22:25:13.546 UTC
SummalyBot/5.1.0
0
no JS
2026-07-09 22:25:11.730 UTC
SummalyBot/5.1.0
0
no JS
2026-07-05 18:23:16.315 UTC
SummalyBot/5.1.0
0
no JS
2026-07-05 18:23:14.537 UTC
SummalyBot/5.1.0
0
no JS

By user agent

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

User AgentRequestsJS ran
SummalyBot/5.1.0
14 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 SummalyBot/5.1.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)