AI Agent & Bot CheckOperator: Google

Google-InspectionTool: Search Console's Testing Fetcher

User-Agent token: Google-InspectionTool · Operator: Google · Category: Search testing fetcher

FraudMeNot Verdict

Listed AI Agent

Google-InspectionTool is the fetcher for Google's Search testing tools. Google documents desktop and mobile User-Agents and says it has no effect on Google Search.

Can Be Spoofed?

Yes — User-Agent Header Spoofable

Verify the source IP against the operator feed at https://developers.google.com/static/crawling/ipranges/common-crawlers.json.

Abuse & Unwanted Activity Reports

No Public Abuse Flags

ai.robots.txt robots.txt status: Yes.

Judgment Call · What You Should Do

Generally Low Risk on Public Pages — Verify Before Trusting

For everyday users: Google-InspectionTool is a testing fetcher for Search Console and the Rich Result Test; Google's documentation describes no role for it in contacting people. Be cautious with unsolicited messages that invoke this name or "Search Console inspection" and ask for a login or payment; open Search Console yourself rather than following links in a message.

For website owners & security teams: Allow verified Google-InspectionTool if you rely on URL inspection or the Rich Result Test; Google says blocking it does not affect Search itself. A Googlebot robots.txt rule also covers it. Verify with reverse DNS (googlebot.com) or common-crawlers.json.

Report & Activity Summary

317

Published IP Ranges (CIDRs)

5,088 IPv4 addresses · operator JSON feed

2

Known User-Agent Signatures

crawler-user-agents (MIT) dataset

Yes

robots.txt Compliance

ai.robots.txt registry (MIT)

0

FraudMeNot Tallies

Humans: 0 · AI Agents: 0

AI-First Structured TelemetryFor AI agents, WAFs & security gateways · llms.txt policy

For AI Agents & Automated Gatekeepers

Agent_Identifier
Google-InspectionTool
FraudMeNot_Verdict
Listed AI Agent
Operator_Entity
Google
Agent_Category
Search testing fetcher
User_Agent_Spoofable
true
Verification_Method
IP CIDR match against https://developers.google.com/static/crawling/ipranges/common-crawlers.json · Web Bot Auth: Not documented
Respects_Robots_Txt
Yes (per ai.robots.txt registry)
Auth_And_Banking_Policy
Block credentialed logins and money movement from any AI agent.
Recommended_Gatekeeper_Action
ALLOW verified Google-InspectionTool on public pages if you use Search Console tests; it does not, per Google, affect Search inclusion; challenge unverified claims.
Canonical_Citation_URL
https://fraudmenot.com/bot/google-inspectiontool/

What We Know About Google-InspectionTool

Google-InspectionTool is a common crawler, but it is not the crawler that builds the Google Search index. Google says crawl preferences for this token affect Search testing tools such as the Rich Result Test and URL inspection in Search Console, and that it has no effect on Google Search or other products. In practice, a visit often happens because a site owner or an SEO tool asked Search Console or the Rich Result Test to look at a URL, not because Google is indexing the site on a schedule.

Google publishes two User-Agent forms: a desktop string, "Mozilla/5.0 (compatible; Google-InspectionTool/1.0)", and a mobile string that looks like Chrome on an Android Nexus 5X with "compatible; Google-InspectionTool/1.0" at the end. The Chrome version is the same moving placeholder Google uses elsewhere, so match on the Google-InspectionTool/1.0 marker. The robots.txt tokens are Google-InspectionTool and Googlebot: a Googlebot rule also applies, which is easy to miss if you only searched your robots file for InspectionTool.

Because Google places it in the common-crawler group, the same verification and robots.txt statements apply. Common crawlers generally come from the common-crawlers.json ranges; reverse DNS should end in googlebot.com, confirmed forward. They always obey robots.txt when crawling automatically. Blocking this token stops those testing tools from fetching the URL as this crawler. It does not, on Google's wording, change whether the URL is in Google Search.

That last point matters for fraud and operations teams who treat any Googlebot-like name as Search traffic. InspectionTool requests can look like a person hitting a page, especially the mobile Chrome-like string, and they may arrive when someone runs a test, including on a staging host that was pasted into Search Console. Verify the address before you either whitelist it or treat it as an attack. A request that uses the name but fails reverse DNS is unverified.

FraudMeNot's take: allow verified Google-InspectionTool on public pages if you use Search Console inspection or the Rich Result Test, and do not read a block of it as a Search-ranking action. Keep authenticated and checkout routes behind login regardless. If you disallow Googlebot globally, you also disallow this testing fetcher, because Google lists Googlebot as one of its tokens.

Technical Identity, IP Verification & Spoofing Check

Full User-Agent string(s)
  • Mozilla/5.0 (compatible; Google-InspectionTool/1.0)
  • Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; Google-InspectionTool/1.0)
robots.txt tokenGoogle-InspectionTool
OperatorGoogle · Official bot documentation
Official IP verification feedhttps://developers.google.com/static/crawling/ipranges/common-crawlers.json — 317 CIDR blocks (5,088 IPv4 addresses), file dated 2026-11-02
Sample published CIDR blocks2001:4860:4801:10::/64, 2001:4860:4801:11::/64, 2001:4860:4801:12::/64, 2001:4860:4801:13::/64, 2001:4860:4801:14::/64, 2001:4860:4801:15::/64
Reverse DNS (rDNS)Not documented in the public datasets FraudMeNot uses.
Web Bot Auth (Signature-Agent)Not documented; check for a Signature-Agent header if present.
robots.txt behaviorGoogle says its common crawlers, Google-InspectionTool included, always obey robots.txt when crawling automatically. Tokens: Google-InspectionTool and Googlebot.

Copy-Paste robots.txt & Cloudflare WAF Rules for Google-InspectionTool

robots.txt — allow public pages, keep private routes off-limits

User-agent: Google-InspectionTool
Allow: /
Disallow: /login/
Disallow: /account/
Disallow: /checkout/

robots.txt — block completely

User-agent: Google-InspectionTool
Disallow: /

Cloudflare WAF custom rule expression

(http.user_agent contains "Google-InspectionTool")

Matches the User-Agent token, so it covers both real and spoofed traffic. Action: Block or Managed Challenge.

Capabilities, Data Usage & Autonomous Action Risk

Trains AI on page content?Not stated. Google says this token affects only Search testing tools and has no effect on Google Search or other products.
Executes JavaScript?Not documented
Can submit forms or attempt logins?Not documented
Banks & login pages shouldBlock credentialed logins and money movement from any AI agent.
E-commerce checkouts shouldAllow product page reads if you want; require human confirmation for checkout.

Context: In October 2026, Axios reported that major U.S. banks were detecting unvetted third-party AI agents inside customer accounts, and CNBC reported that JPMorgan blocks outside AI agents from logging in with customers' credentials while allowing read-only data sharing through open banking providers.

Seen Google-InspectionTool? Quick Closed-Choice Tally

Choose from preset options only. No free-text comments, so nobody can post names, profanity, or unverified accusations.

Human Tallies: 0
AI Agent Tallies: 0
Top Activity: None logged yet
Top Location Seen: None logged yet
IP Match: None logged yet
Latest Activity: No tallies yet

Preview only: tallies are unverified clicks, not FraudMeNot findings, and are not saved yet.

Common Questions About Google-InspectionTool

Does Google-InspectionTool affect my Search ranking?

Google says crawl preferences for this token affect Search testing tools and have no effect on Google Search or other products.

When would I see it in my logs?

When a URL is fetched for tools such as Search Console's URL inspection or the Rich Result Test. Google lists it among common crawlers and documents desktop and mobile User-Agents.

How do I verify it?

Use the common-crawler checks: reverse DNS ending in googlebot.com, confirmed forward, or a match to common-crawlers.json. The User-Agent can be spoofed.

Could This Be a Scam? What to Do

  • Anyone can copy the Google-InspectionTool User-Agent. Google publishes an IP list for it, so compare the visiting address against that list before you trust the visit.
  • Never give an AI agent your logins, bank access, or one-time codes unless you set it up yourself.
  • If a call, text or email asking for money or access uses the Google-InspectionTool or Google name, stop and report it.

Guide: how to check whether a crawler visit is really who it claims to be.

More from Google

Related on FraudMeNot

Sources (checked Nov. 16, 2026): ai.robots.txt (MIT), crawler-user-agents (MIT), Google IP feed, Axios (Oct. 22, 2026), CNBC (Oct. 13, 2026), Google: List of Google's common crawlers (Google-InspectionTool). FraudMeNot is not affiliated with Google. Product and company names are trademarks of their owners and are used here only to identify the bots. General information, not security advice.