Verifying Googlebot: reverse DNS vs IP-range matching

Verifying Googlebot: reverse DNS vs IP-range matching

Two ways to prove a bot is real, and the tradeoff is freshness vs speed. Credited to Google's own crawler docs.

→ Reverse + forward DNS — the method Google documents: PTR lookup, confirm it ends in googlebot.com, then forward-resolve back. Bulletproof, but it's a network call per IP.
→ Published IP ranges — Google now ships googlebot.json. Match against the CIDR blocks offline, no DNS round-trips. Faster for batch jobs over millions of lines.

⭐ Pick of the week: Google's note that the JSON list is the canonical source — but they still update it, so cache it daily, don't hardcode.

Takeaway: reverse DNS for live, low-volume checks; the IP-range JSON for batch verification where DNS latency would kill you.