Bingbot

Microsoft · AI search indexer

Microsoft Bing's search crawler. Microsoft publishes its IP list for verification.

User-agent contains
Bingbot
robots.txt token
bingbot
Respects robots.txt
Yes, per operator docs
Official IP ranges
28 prefixes

How to verify Bingbot

Matching the user agent isn't enough, because any client can send it. A real Bingbot request comes from an IP address inside Microsoft's published list:

The quickest way to check a whole log is our free log checker. It runs in your browser and splits Bingbot requests into real and fake.

First 20 prefixes
157.55.39.0/24
207.46.13.0/24
40.77.167.0/24
13.66.139.0/24
13.66.144.0/24
52.167.144.0/24
13.67.10.16/28
13.69.66.240/28
13.71.172.224/28
139.217.52.0/28
191.233.204.224/28
20.36.108.32/28
20.43.120.16/28
40.79.131.208/28
40.79.186.176/28
52.231.148.0/28
20.79.107.240/28
51.105.67.0/28
20.125.163.80/28
40.77.188.0/22

Block or allow Bingbot in robots.txt

User-agent: bingbot
Disallow: /

Use Allow: / instead to explicitly permit it, or build a full file with the AI robots.txt generator. robots.txt is a request, not a lock: it only works for bots that honor it, and only real Bingbot traffic would.

Verify Bingbot automatically

One API call tells your app, WAF or middleware whether a request claiming to be Bingbot really comes from Microsoft's official IP ranges.

Get a free API key10,000 checks/month free · Pro $19/month for 1M