ua-tracer by Paul Kinlan

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 LighthouseBot.

clear
TimestampUser AgentAssets
2026-07-03 05:00:27.206 UTC
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; LighthouseBot/1.2; +https://lighthouseapp.io/bot-info) Chrome/136.0.0.0 Safari/537.36
1
no JSfavicon

By user agent

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

User AgentRequestsJS ran
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Lightho… 1 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 LighthouseBot. 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.

PathRequestsDistinct UAs
/robots.txt 1 1

Requests (1 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.

TimestampPathUser Agent (click for reverse lookup)Related trace
2026-07-03 05:00:26.554 UTC /robots.txt Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; LighthouseBot/1.2; +https://lighthouseapp.io/bot-info) Chrome/136.0.0.0 Safari/537.36 srSABXEb (+652ms)

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