bingbot

What this client asked www.pathwren.workers.dev for, when, and what it got. Every number below is from this host's own server-side request log, 2026-08-31 20:58:11Z to 2026-09-14 05:57:10Z UTC.

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36
Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)

177 request(s) from 97 distinct address(es), 94 distinct path(s), first seen 2026-08-31 20:58:11Z, last seen 2026-09-14 05:57:10Z UTC. 82 separate visit(s), counting a gap of more than 30 minutes as a new one, median 140.9 minutes between them.

It describes itself, inside its own user-agent, as bingbot/2.0. That is the client's own words, quoted; this page makes no claim about what it is for.

The crawler catalogue on this site has a record for it: /crawler/bingbot.html — what it is for, and what blocking it costs. This page is only what it did here.

The user-agent strings, exactly as they arrived

What it asked for, in the order it asked

First request to each path, oldest first, first 40 shown.

Everything it asked for

34 further paths are in the JSON.

What it asked for that did not exist

Nothing. Every path it asked for existed at the time it asked.

What it got, and what it sent

Status codes

200×176, not recorded×1

Accept headers

*/*

Bytes served

6442630

Attributed to a channel

lemmy (10), pypi-registry (4), mcp-registry-official (3), smithery-direct (2), kaggle-datasets (2), a2a-registry-global (1), piefed (1), indieseek (1), freepublicapis (1)

Our instrument classed it

crawler×177 — that is our classifier's label from the user-agent, not the operator's, and it has been wrong before.

How to verify it is really them

published IP ranges The published ranges we mirror for it are at /ip-ranges/bing-bingbot.html.

From the crawler record at /crawler/bingbot.html, which cites https://www.bing.com/webmasters/help/which-crawlers-does-bing-use-8c184ec0 — one source for both pages.

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/classify-ua?ua=Mozilla%2F5.0%20AppleWebKit%2F537.36%20%28KHTML%2C%20like%20Gecko%3B%20compatible%3B%20bingbot%2F2.0%3B%20%2Bhttp%3A%2F%2Fwww.bing.com%2Fbingbot.htm%29%20Chrome%2F116.0.1938.76%20Safari%2F537.36&s=client-dossiers'

• /tools/classify-ua?ua=Mozilla%2F5.0%20AppleWebKit%2F537.36%20%28KHTML%2C%20like%20Gecko%3B%20compatible%3B%20bingbot%2F2.0%3B%20%2Bhttp%3A%2F%2Fwww.bing.com%2Fbingbot.htm%29%20Chrome%2F116.0.1938.76%20Safari%2F537.36
  What is Mozilla/5.0 AppleWebKit/537.36 (KHTML, like G…? This exact user-agent run through the catalogue: which crawler it is, who operates it, what the crawl is for, what blocking it costs — or an honest "not recognised" if it is nobody we know.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

What it publishes about you afterwards

Not observed. We have not seen this client publish a grade, a listing or a record about this host anywhere, and we make no claim that it does or does not.

Its own documentation

It names http://www.bing.com/bingbot.htm in its own user-agent. That is the operator's own claim about itself; we neither endorse nor verify what is on it.

This page as data

curl -s https://www.pathwren.workers.dev/bot/bingbot.json
curl -s https://www.pathwren.workers.dev/data/observed-clients.json   # every client, one request

JSON · markdown · all clients seen here · index as JSON · check a crawler yourself, no key

Method, and what this page will not say

Rows come from a server-side log written before anything is served, so clients that run no JavaScript are counted exactly like browsers. The window is the whole life of the log, 2026-08-31 20:58:11Z to 2026-09-14 05:57:10Z UTC, and it is stated on every number because a count without a window is not a fact. Addresses are stored as salted hashes and counted, never printed. Our own checks send X-Self: 1 and are excluded, together with every request the analyst flagged as one of our own agents reaching for a URL through a model provider's fetch tool (the numbers are on the index). Nothing here is a claim about intent: where this page does not know something it says not observed.