Network identity
GrowGanic crawler and publishing IPs
Addresses last verified 2026-08-27
GrowGanic writes and publishes articles on behalf of the people who own the sites it connects to. This page exists so a hosting provider, firewall or security plugin can identify that traffic and tell it apart from everything else. If you are a customer whose host is blocking us, the request to send them is at the bottom.
IP addresses we connect from
Every request GrowGanic makes to a customer site originates from one of these four addresses. They are static. We do not rotate them, and we publish them here precisely so that they can be allowlisted.
152.55.176.240 152.55.177.181 152.55.177.193 162.220.232.251
Most control panels and support desks prefer ranges, and several cap how many entries you may add. The same four addresses as three /24 ranges:
152.55.176.0/24 152.55.177.0/24 162.220.232.0/24
Machine-readable at /crawler/ips.json.
User-Agents we send
Two, and only two. Both are stable and neither is ever disguised when talking to a site we have been given credentials for.
Publishing. Connection checks, article publishes, updates and image uploads to a customer's CMS:
GrowGanic/1.0 (+https://growganic.io)
Site audit. Reading a customer's own pages to score them for technical SEO:
GrowGanicBot/1.0 (+https://growganic.io/crawler)
What the traffic does
Publishing is authenticated, always. Requests to a CMS carry credentials the site owner issued to us themselves, such as a WordPress Application Password. Allowing our addresses through a bot challenge does not create an anonymous way in. Anything arriving from them still has to present those credentials before the CMS will accept a single word.
Crawling is light and consented. We only ever crawl a site whose owner connected it to GrowGanic. A site audit reads a bounded set of that site's own pages, a few times a month, one request at a time. We are not a search index and we do not follow links off the domain we were given.
We honour robots.txt for the audit crawler. If you would rather we did not read a particular path, disallow GrowGanicBotand we will skip it. Note that this also removes those pages from the owner's own SEO scoring, which is usually not what they want.
If we are being blocked
The usual symptom is that a security layer answers our request with a challenge page instead of passing it to the API, so publishing fails with what looks like a malformed response. Anti- bot systems on shared hosting flag us on the address, not the User-Agent, because a cloud address looks like a datacenter no matter what it calls itself. Allowing the three ranges above is what resolves it.
Send this to your host, or paste it into a support ticket:
Please add a firewall / anti-bot exception for the following IP ranges on my domain: 152.55.176.0/24 152.55.177.0/24 162.220.232.0/24 These are the published addresses of GrowGanic, a publishing tool I use. It connects to my WordPress REST API at /wp-json/wp/v2/ to post articles, and it is currently being served a security challenge page instead of the API. Every request is authenticated with a WordPress Application Password that I issued, so the exception does not create an anonymous way in. The addresses and the identifying User-Agents are published at https://growganic.io/crawler
Reaching us
If our traffic is causing a problem on your infrastructure, or you need something added to this page to write a rule against, write to [email protected] and a person will answer. We would much rather hear from you than be quietly blocked.