Verified Bingbot is not returning expected hostname as per guidelines

Copper Contributor

As per the official guidelines at:, to verify we a bingbot,

  1. Perform a reverse DNS lookup using the IP address from the logs to verify that it resolves to a name that end with
  2. Do a forward DNS lookup using the name from step 1 to confirm that it resolves back to the same IP address


Now, I received requests from the subnet "" with a user agent of:

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Mobile Safari/537.36 (compatible; bingbot/2.0; +


Given the "bingbot" in user agent, when I do step 1 of verifying the bot, I do not get a proper hostname. Some IP lookup tools just return the IP address itself while some say "No valid reverse DNS data is received from host. Try again later." and others do not return any hostname at all.


So all the IPs in this subnet fail step 1 (reverse DNS check) and hence should be considered as someone spoofing? But then,

A. As per official IP Address list, Bing is in fact claiming this subnet to be an official IP range used by bingbot!!?

B. When validating any IP address from the mentioned subnet using the official "Verify Bingbot" tool at:, then again it says that it is an valid bingbot IP!!

Why this inconsistency and what to conclude? 

Additionally, When I looked up a few IPs on AbuseIP database, I see all of them being getting reported.

If the IP is not returning proper hostname then how to trust it?

I want Bing to index my pages though I do not want any malicious traffic.

0 Replies