Bing seems to be spidering from a new range of IPs.
jmccormac
9:28 pm on Sep 20, 2023 (gmt 0)
Just noticed Bingbot coming from a new range of Microsoft IPs (20.15.133.ddd). It kept getting blocked. The IPs check out according to Bing's "Verify Bingbot" tool.
Regards...jmcc
not2easy
9:48 pm on Sep 20, 2023 (gmt 0)
20.15.133.160/27 is now listed for bingbot, not on my older list.
Three IPs from the range were getting rate limited. That json file of bingbot IPs is useful. It will be great when Bing's backend people work out how to use 304s for sitemap files..
Regards...jmcc
SumGuy
10:59 pm on Oct 4, 2023 (gmt 0)
First bingbot hit ever from 20.15.0.0/16 today. IP was 20.15.133.167. UA was
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/103.0.5060.134 Safari/537.36
Now, I was IP blocking that /16 in the router up until a month or so ago, I'd never have known it was knocking on my door except to notice it was brought up in this thread.
I block ALL MSFT IP's (and Goog, AWS, Digital Ocean, Hetzner just to name some big players) in my router so their garbage hits don't pollute my web and mail server logs. Only /16's that contain known / good bots and mail servers are allowed through. Troublesome IP's within the known/good /16's are dealt with at a more granular level as needed.
