Bingbot IP Ranges
Bingbot is the crawler that builds Microsoft's Bing index, which also feeds the search results of several other engines and assistants that license it. Microsoft publishes its addresses in one file of 28 IPv4 prefixes and no IPv6, 4,736 addresses in all. Bingbot runs on Microsoft's own network, AS8075, the same one that carries the OpenAI and DuckDuckGo robots elsewhere on this site, so the AS number alone does not tell those crawlers apart.
- Provider
- Bingbot
- Hosting network
- AS8075 (Microsoft, host)
- Category
- Crawler
- Headquarters
- Redmond, WA, USA
- Published IPv4 prefixes
- 28
- Registry
- Self-published list
Known IP ranges
Microsoft does not announce these addresses under an ASN of its own. They are the prefixes it publishes in https://www.bing.com/toolbox/bingbot.json, as fetched on 2026-10-16; the space itself is routed by AS8075 (Microsoft). The list decides whether an address belongs to Bingbot - WHOIS for any of them returns the host network.
40.77.188.0/22
40.77.178.0/23
199.30.24.0/23
13.66.139.0/24
13.66.144.0/24
40.77.167.0/24
40.77.177.0/24
40.77.202.0/24
52.167.144.0/24
65.55.210.0/24
What does a Bingbot IP mean in a privacy test?
A Bingbot address is Microsoft's search crawler reading a page, never a person. Because AS8075 also hosts other companies' robots, confirm Bingbot by the list or by DNS rather than by the network name.
A small list that rarely changes
The file is www.bing.com/toolbox/bingbot.json. Fetched on 16 October 2026, its creationTime still read 3 January 2024, so unlike Google's files, which are regenerated daily, Bing's has gone almost two years without a change. That makes it easy to cache, and it also means a request from a new Microsoft address claiming to be Bingbot deserves a DNS check before the list is assumed incomplete.
The 28 prefixes vary widely in size: one /22, two /23s, nine /24s, one /25, one /27 and fourteen /28s. They spread across several Microsoft blocks, eight in 40.0.0.0/8, six in 20.0.0.0/8 and five in 13.0.0.0/8, rather than sitting in one dedicated range.
Bingbot versus everything else on AS8075
AS8075 is one of the largest networks in the world and carries Azure customers as well as Microsoft's own services, so an AS8075 address on its own is no evidence of Bingbot. Microsoft documents a DNS test instead: a reverse lookup on a genuine Bingbot address returns a name under search.msn.com, and the forward lookup on that name returns the address again.
The same network hosts the OpenAI crawlers and DuckDuckBot, which publish their own lists, so a log full of AS8075 addresses can be three different companies' robots plus ordinary Azure traffic. Matching each address against the right list is the only way to separate them.
Related tools
Frequently asked questions
What IP ranges does Bingbot use?
The 28 IPv4 prefixes in bing.com/toolbox/bingbot.json, from a /22 down to /28s, 4,736 addresses in all, every one inside Microsoft's AS8075. There is no IPv6 in the list.
Why does a Bingbot address appear in my logs or a privacy test?
A Bingbot address is Microsoft's search crawler reading a page, never a person. Because AS8075 also hosts other companies' robots, confirm Bingbot by the list or by DNS rather than by the network name.
How do I verify a Bingbot request?
Match the address against bingbot.json, or run a reverse DNS lookup: a real Bingbot address resolves to a name under search.msn.com, and that name resolves forward to the same address.
Why hasn't the Bingbot list changed since 2024?
Its creationTime still read 3 January 2024 in October 2026. Microsoft has kept the crawler on the same blocks; a Microsoft address outside the list is more likely another Azure tenant than a new Bingbot range.
Is every Microsoft AS8075 address a Bing crawler?
No. AS8075 also carries Azure customers and, among others, the OpenAI and DuckDuckGo crawlers. Only the 28 prefixes in bingbot.json belong to Bingbot.