adidxbotBing says AdIdxBot is the crawler used by Bing Ads. It crawls ads and follows the websites from those ads for quality control, with desktop and mobile variants. The row title is AdIdxBot. The published strings contain adidxbot/2.0. The help URL HTML is an application shell. The article was read from the help API that page loads, ArticleId 8c184ec0. The page says robots.txt files can be configured to tell Bing crawlers how to interact with the site. It does not say that this crawler obeys every directive. This check matches the whole token and still reports the RFC 9309 decision.
ads_checktells_how_to_interact. The vendor says a robots.txt file can be configured to tell this crawler how to interact with the site. The cited page does not say that the crawler obeys every directive.Mozilla/5.0 (compatible; adidxbot/2.0; +http://www.bing.com/bingbot.htm) The row title is AdIdxBot. The page also prints an iPhone string and a Windows Phone string, both containing adidxbot/2.0 and +http://www.bing.com/bingbot.htm. The iPhone string is Mozilla/5.0 (iPhone; CPU iPhone OS 7_0 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Version/7.0 Mobile/11A465 Safari/9537.53 (compatible; adidxbot/2.0; +http://www.bing.com/bingbot.htm). The Windows Phone string names Lumia 530. The page does not print a separate robots.txt User-agent line.curl -s https://whosthatbot.com/v1/crawlers/adidxbot
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows adidxbot on /docs and allows *. The call does not fetch a host.
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: adidxbot\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["adidxbot"]}}}'
That call returns fetched_target false. This row is disallow via group adidxbot, rule Disallow: /.