Guides › Hosting, domain & email › Security & hacks

Verify Googlebot vs Fake Bots: Reverse DNS Check

Verification.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Security and hacking

Some bots pretend to be Googlebot to get past your defences. You can check whether a visitor really is Google with a two-step DNS test.

1Find the IP address2Run a reverse lookup3Run a forward lookup4Block or limit fakes5Do not block real Googlebot6Use Google's published listFixed? Test the site. If not, get help.
The steps in order. Work down the list and stop when the problem is solved.

Step 1: Find the IP address

Illustration for Step 1: Find the IP address

Open your server's access log (in cPanel look for Raw Access or Metrics, Visitors). Find the IP address of the request that claims to be Googlebot in its user agent.

Step 2: Run a reverse lookup

Illustration for Step 2: Run a reverse lookup

On a computer with a terminal run host 66.249.66.1, replacing the number with the real IP. The reply should name a host ending in googlebot.com or google.com.

Step 3: Run a forward lookup

Illustration for Step 3: Run a forward lookup

Now run host on the name you got. It must return the same IP address you started with. If it returns a different address, the bot is fake.

Step 4: Block or limit fakes

Illustration for Step 4: Block or limit fakes

If either check fails, block the IP in your firewall or rate-limit it in Cloudflare or your security plugin.

Step 5: Do not block real Googlebot

Illustration for Step 5: Do not block real Googlebot

Never block all traffic that says Googlebot in its user agent. Verify first, since blocking the real one removes you from search.

Step 6: Use Google's published list

Illustration for Step 6: Use Google's published list

Google also publishes its crawler IP ranges, which you can use to allow-list real crawlers.

Still stuck?

If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.

Related guides

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-22.