Definition
Reverse DNS verification is a check that a visitor claiming to be a known bot really comes from that bot's operator. You look up the hostname for the request's IP address, confirm it ends in the operator's domain, then look up that hostname and confirm it points back to the same IP address.
Why it matters
Anyone can send a request with "Googlebot" in the User-Agent header. Reverse DNS verification tests the part that is hard to fake: the network address the request came from. Google says this check "is useful if you're concerned that spammers or other troublemakers are accessing your site while claiming to be from Google."
If you give known bots special treatment, such as skipping a rate limit or a firewall rule, this check stops requests that only borrow a name from getting the same treatment.
How it works
Google documents four steps:
- Run a reverse DNS lookup on the IP address from your logs.
- Check that the hostname ends in the operator's domain. For Google that is googlebot.com, google.com or googleusercontent.com.
- Run a forward DNS lookup on that hostname.
- Check that it returns the same IP address you started with.
Both directions matter. Whoever controls an IP address can make its reverse lookup return any name, but only the real domain owner controls what that name resolves to going forward.
Reverse DNS is not the only check. Many operators publish lists of IP addresses that you match against. OpenAI, for example, publishes JSON files of addresses for GPTBot, OAI-SearchBot and ChatGPT-User. Google publishes IP lists too, as an alternative to DNS lookups. Cloudflare counts reverse DNS, a published IP list with a stable user agent, and a Web Bot Auth signature among the ways a bot can identify itself honestly.
Example
Your logs show a request claiming to be Googlebot from 66.249.66.1. You run:
$ host 66.249.66.1
1.66.249.66.in-addr.arpa domain name pointer crawl-66-249-66-1.googlebot.com.
$ host crawl-66-249-66-1.googlebot.com
crawl-66-249-66-1.googlebot.com has address 66.249.66.1
The hostname is under googlebot.com and points back to the same address, so the request is verified. If the first lookup returned an unrelated hostname, or none, you would have a request that claims to be Googlebot but fails verification. See verified bot and fake GPTBot, ClaudeBot and Googlebot.
Sources
- Google: Verify requests from Google crawlers and fetchers · checked 16 Nov 2026
- OpenAI: Overview of OpenAI crawlers · checked 16 Nov 2026
- Cloudflare: Verified bots · checked 16 Nov 2026