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 NetAPI/1.1 (+https://netapi.com/bot.html).

clear
TimestampUser AgentAssets
2026-11-08 05:44:07.072 UTC
NetAPI/1.1 (+https://netapi.com/bot.html)
0
no JS—
2026-10-29 01:29:47.148 UTC
NetAPI/1.1 (+https://netapi.com/bot.html)
0
no JS—
2026-10-19 21:14:39.696 UTC
NetAPI/1.1 (+https://netapi.com/bot.html)
0
no JS—
2026-10-09 20:41:24.234 UTC
NetAPI/1.1 (+https://netapi.com/bot.html)
0
no JS—

By user agent

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

User AgentRequestsJS ran
NetAPI/1.1 (+https://netapi.com/bot.html)
4 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 path /robots.txt to user agent NetAPI/1.1 (+https://netapi.com/bot.html). 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-11-08 05:44:06.199 UTC /robots.txt NetAPI/1.1 (+https://netapi.com/bot.html) —

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