Crawling and indexing
How do you verify a crawler with reverse DNS?
A reverse DNS lookup turns a request's IP address into a host name. To verify a crawler, look up the IP, check the name ends in the operator's domain, such as googlebot.com, then look up that name and confirm it returns the same IP. A user agent alone proves nothing.
How to read it
The forward lookup matters. Anyone can set reverse DNS for their own IP to say googlebot.com; only Google's own DNS returns the same IP for that name.
Some operators publish IP ranges instead, and some sign requests. Your CDN may do the check for you: Cloudflare marks requests it verified as verified bots.
Example from rankecho.io
847 requests claimed to be Googlebot
In 30 days, Cloudflare verified 1,751 Googlebot requests to rankecho.io. Another 847 used Googlebot's user agent without passing that check, and 114 of them asked for secret files such as /.env.
Treating every "Googlebot" request as Google would have let those through any rule written for Google.
Source: rankecho.io's Cloudflare logs, verified and unverified requests, 17 October to 15 November 2026.
Questions people ask
How do you verify a crawler with reverse DNS?
A reverse DNS lookup turns a request's IP address into a host name. To verify a crawler, look up the IP, check the name ends in the operator's domain, such as googlebot.com, then look up that name and confirm it returns the same IP. A user agent alone proves nothing.
Can I verify AI crawlers the same way?
Some, such as Applebot and Amazonbot, support reverse DNS. OpenAI, Anthropic and Perplexity publish IP ranges instead. Each crawler's page on rankecho.io says how.
Is checking the user agent enough?
No. Any client can send any user agent.
Related terms
Read more on rankecho.io
See it on your own site
RankEcho reads your Search Console data and asks AI assistants whether they cite you, then shows each of these numbers for your pages. The audit is free.
Definition and example checked 2026-11-16.
