-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Referrer-Domain] Microsoft Search Engine Spiders are blocked! #534
Comments
Please post some log line examples |
Hello, 2024-03-30 21:48:43,595 fail2ban.filter [743]: INFO [nginxrepeatoffender] Found 40.77.167.41 - 2024-03-30 21:48:43 |
any one may try this regex for MS Clarity and MS Search but I am not sure it is 100% correct. "~*(?:\b)msnbot-'\b((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)(-|$)){4}\b'.search.msn.com(?:\b)" 0; |
another one gives these to check IPv4 |
MS Search IPs are still banned today!!! |
I need to see your web access log not the fail2ban log |
Hello, 2 more records from today. 40.77.167.50 - - [16/Sep/2024:19:59:41 +0800] "GET /search?l=20386&distance=300&c=1 HTTP/2.0" 200 16164 "-" "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" |
According to this log all the bingbots are getting a 200 OK and some are getting a 404 NOT FOUND - so according to this they are not being blocked unless they got a 444 error (default) |
I see. Thanks for your reply. |
New MS Search 444 access today. Please advise. |
My sites have joined MS Clarity and MS search spiders began to crawl my sites frequently. nginxrepeatoffender began to jail their IPs.
Their general domain names are:
msnbot-xxx-xxx-xxx-xxx.search.msn.com
How do I whitelist them? In where xxx-xxx-xxx-xxx is a general IPv4 IP address.
The text was updated successfully, but these errors were encountered: