Microsoft's search crawler. It fetches pages so they can be indexed in Bing. Intent: search index. Stores your pages so they can show up in search results.

What is the Bingbot user agent?

Requests from Bingbot carry "bingbot" in the User-Agent header (matching is case-insensitive). The full string includes a version number that changes over time; Microsoft's documentation lists the current one. In robots.txt, the token is Bingbot.

How do I verify Bingbot?

Microsoft publishes the IP ranges Bingbot uses, and its reverse DNS ends in .search.msn.com. Paste an IP into HadoSEO's free bot verifier to check it against the published data.

How do I block Bingbot in robots.txt?

Add "User-agent: Bingbot" followed by "Disallow: /" to your robots.txt. robots.txt is a request, not a lock: a scraper using Bingbot's name ignores it, which is why verification matters.

Can I see when Bingbot visits my site?

Yes. HadoSEO logs every Bingbot request by page, checks it against Microsoft's published data, and flags requests that use the name from IPs Microsoft doesn't own. For a one-off look, the free log file analyzer reads a week of your server logs in the browser.

[ search crawler · Microsoft ]

Bingbot: Microsoft's search crawler.

Microsoft's search crawler. It fetches pages so they can be indexed in Bing. Its intent is search index: stores your pages so they can show up in search results.

search indexverifiable by published IP ranges

IP ranges last updated Oct 25, 2026

Check a Bingbot IP All AI crawlers

[ technical facts ]

operator: Microsoft
intent: search index
user agent contains: bingbot
robots.txt token: Bingbot
verification: published IP rangesverified
reverse DNS: .search.msn.com
official IP list: www.bing.com/toolbox/bingbot.json
ranges in registry: none loaded (source unreachable at last refresh)
last updated: Oct 25, 2026
operator docs: www.bing.com/webmasters/help/verifying-bingbot-2195837f

[ verify ]

How to verify a real Bingbot request.

Microsoft publishes the IP ranges Bingbot uses, and its reverse DNS ends in .search.msn.com.

01Check the User-Agent header contains "bingbot" (case-insensitive). That is only a claim: anyone can send it.
02Download Microsoft's published list (https://www.bing.com/toolbox/bingbot.json) and check the request IP falls inside one of its ranges.
03Optionally confirm reverse DNS: the IP's hostname ends in .search.msn.com and resolves back to the same IP.
04Inside the list: the real Bingbot. Outside it: a request using Bingbot's name from someone else's server.

Skip the lookups: the free bot verifier checks one IP against the same registry, and the log file analyzer checks every Bingbot request in a week of access logs. Requests that fail are flagged as spoofed, not hidden.

[ robots.txt ]

Block or allow Bingbot in robots.txt.

Add one of these groups to the robots.txt at your domain root. The token matches case-insensitively.

block Bingbot

User-agent: Bingbot
Disallow: /

allow Bingbot

User-agent: Bingbot
Allow: /

robots.txt only binds crawlers that choose to follow it. A scraper sending Bingbot's user agent from its own servers won't, which is why HadoSEO checks the IP behind every request.

[ questions ]

Bingbot, answered.

[ free scan ]