GuzzleHttp is software in the HTTP clients and libraries category.
GuzzleHttp is the default user agent of Guzzle, a PHP HTTP client used by many PHP applications and plugins.
HTTP clients are programming libraries and command line tools. Developers use them for scripts, integrations and scrapers. Real browsers never send these user agents, so treat them as automated traffic and block them on pages meant for people.
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.
We have not confirmed whether GuzzleHttp 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: GuzzleHttp Disallow: /
User-agent: GuzzleHttp Disallow: /private/ Disallow: /search
User-agent: GuzzleHttp Allow: /blog/ Disallow: /
User-agent: GuzzleHttp Allow: / User-agent: * Disallow: /
User-agent: GuzzleHttp group, GuzzleHttp ignores your User-agent: * rules, so repeat any that should still apply.GuzzleHttp from GuzzleHttp's user agent; check the operator'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.
GuzzleHttp is a common tool for scrapers. Real readers never use it, so block it on article pages and keep it out of ad requests.
Transfon Security for publishersTraffic from GuzzleHttp on landing pages is automated. It inflates clicks and visits, so filter it from campaign data and raise it with the ad network.
Transfon Security for advertisersPrice scrapers, stock checkers and card testing scripts often run on GuzzleHttp. Block it on product, cart and checkout pages.
Transfon Security for e-commerceGuzzleHttp is normal for API clients but not for your web app. Allow it only on API routes that need a key, and rate limit it there.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows GuzzleHttp 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
GuzzleHttp is software in the HTTP clients and libraries category. GuzzleHttp is the default user agent of Guzzle, a PHP HTTP client used by many PHP applications and plugins.
We have not confirmed whether GuzzleHttp 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: GuzzleHttp" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "GuzzleHttp/" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so GuzzleHttp may not follow it, and anyone can send GuzzleHttp's user agent, so a fake GuzzleHttp ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
HTTP clients are programming libraries and command line tools. Developers use them for scripts, integrations and scrapers. Real browsers never send these user agents, so treat them as automated traffic and block them on pages meant for people.
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.