GoogleSafety is a bot in the security scanners category, operated by Google.
The Google-Safety user agent handles abuse-specific crawling, such as malware discovery for publicly posted links on Google properties
Security scanners probe sites for vulnerabilities, certificates and exposed services. Some are research projects, some are vendors you hired. Allow your own scanners and block the rest at the WAF.
Sample user agent strings sent by GoogleSafety:
Google-SafetyMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 (compatible; Google-Safety; +http://www.google.com/bot.html)Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Google-Safety; +http://www.google.com/bot.html)Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
Share of GoogleSafety requests to sites protected by Transfon Security in the 7 days to 27 October 2026.
| United States | 100% |
| Google LLC AS15169 | 100% |
Genuine GoogleSafety IPs resolve to hostnames ending in google.com. Run a reverse DNS lookup on the IP, then a forward lookup on the hostname, and check both match:
host 203.0.113.10 # the IP from your logs host crawl-name.google.com # must return the same IP
We have not confirmed whether GoogleSafety follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: Google-Safety Disallow: /
User-agent: Google-Safety Disallow: /private/ Disallow: /search
User-agent: Google-Safety Allow: /blog/ Disallow: /
User-agent: Google-Safety Allow: / User-agent: * Disallow: /
User-agent: Google-Safety group, GoogleSafety ignores your User-agent: * rules, so repeat any that should still apply.Google-Safety from GoogleSafety's user agent; check Google's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Allow GoogleSafety if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersGoogleSafety is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow GoogleSafety only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf GoogleSafety is a service you use, allow it on the endpoints it needs and block it elsewhere.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows GoogleSafety by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
GoogleSafety is a bot in the security scanners category, operated by Google. The Google-Safety user agent handles abuse-specific crawling, such as malware discovery for publicly posted links on Google properties
We have not confirmed whether GoogleSafety follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.
Add "User-agent: Google-Safety" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "Google-Safety" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so GoogleSafety may not follow it, and anyone can send GoogleSafety's user agent, so a fake GoogleSafety ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Run a reverse DNS lookup on the IP. Genuine GoogleSafety IPs resolve to a hostname ending in google.com, and a forward lookup of that hostname returns the same IP. Anything else using its user agent is an impersonator.
Security scanners probe sites for vulnerabilities, certificates and exposed services. Some are research projects, some are vendors you hired. Allow your own scanners and block the rest at the WAF.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.