--- title: "Serpwise Origin Fetch IP Addresses" description: "Review the IPv4 addresses Serpwise uses to fetch customer origin pages, with roles, locations, hostnames, and verification steps for secure allowlisting." url: "https://serpwise.ai/ips/" source: "https://serpwise.ai/ips/" --- For hosting providers # SerpWise IP addresses SerpWise is an edge SEO proxy. Site owners point their domain at us, and we fetch pages from their origin server and serve them to their visitors. The addresses below are the ones that make those fetches. **If one of your customers is proxied through SerpWise:** traffic reaching your server from these addresses is that customer's own visitors, requested through a proxy their site owner configured deliberately. Rate limiting or bot-challenging these addresses degrades the live site for real people, and the site owner usually cannot tell why. Please allowlist them. ## Addresses 37 addresses · IPv4 · also available as [/ips.txt](/ips.txt) (plain, one per line) and [/ips.json](/ips.json) | Address | Reverse DNS | Location | |-----------------|---------------------------------|-----------------| | 5.161.16.121 | egress-us-east-4.serpwise.ai | Ashburn, US | | 5.161.16.238 | egress-us-east-5.serpwise.ai | Ashburn, US | | 5.161.18.71 | egress-us-east-2.serpwise.ai | Ashburn, US | | 5.161.19.185 | egress-us-east-3.serpwise.ai | Ashburn, US | | 5.161.19.247 | egress-us-east-1.serpwise.ai | Ashburn, US | | 51.68.203.198 | egress-eu-lon-1.serpwise.ai | London, UK | | 51.68.203.205 | egress-eu-lon-2.serpwise.ai | London, UK | | 51.77.46.245 | egress-eu-waw-1.serpwise.ai | Warsaw, PL | | 51.77.47.196 | egress-eu-waw-2.serpwise.ai | Warsaw, PL | | 51.161.52.63 | egress-ca-east-2.serpwise.ai | Beauharnois, CA | | 51.161.52.166 | egress-ca-east-1.serpwise.ai | Beauharnois, CA | | 78.47.38.46 | egress-apex-5.serpwise.ai | Nuremberg, DE | | 91.132.92.136 | egress-eu-cph-5.serpwise.ai | Copenhagen, DK | | 116.202.178.43 | egress-eu-central-3.serpwise.ai | Nuremberg, DE | | 116.202.178.132 | egress-apex-6.serpwise.ai | Nuremberg, DE | | 116.202.182.17 | egress-eu-central-4.serpwise.ai | Nuremberg, DE | | 116.202.183.68 | egress-apex-7.serpwise.ai | Nuremberg, DE | | 116.202.183.149 | egress-eu-central-2.serpwise.ai | Nuremberg, DE | | 116.202.190.183 | egress-apex-8.serpwise.ai | Nuremberg, DE | | 167.233.176.0 | egress-apex-10.serpwise.ai | Nuremberg, DE | | 167.233.178.130 | egress-apex-9.serpwise.ai | Nuremberg, DE | | 167.233.180.16 | egress-apex-3.serpwise.ai | Nuremberg, DE | | 167.233.183.96 | egress-apex-4.serpwise.ai | Nuremberg, DE | | 167.233.186.42 | egress-apex-2.serpwise.ai | Nuremberg, DE | | 167.233.190.83 | egress-eu-central-5.serpwise.ai | Nuremberg, DE | | 178.104.76.247 | edge-apex-1.serpwise.ai | Nuremberg, DE | | 192.36.27.51 | egress-eu-cph-1.serpwise.ai | Copenhagen, DK | | 192.36.27.134 | egress-eu-cph-2.serpwise.ai | Copenhagen, DK | | 192.36.27.167 | egress-eu-cph-3.serpwise.ai | Copenhagen, DK | | 192.36.27.208 | egress-eu-cph-4.serpwise.ai | Copenhagen, DK | | 195.201.45.47 | egress-apex-11.serpwise.ai | Nuremberg, DE | | 195.201.45.222 | egress-apex-15.serpwise.ai | Nuremberg, DE | | 195.201.46.216 | egress-apex-14.serpwise.ai | Nuremberg, DE | | 195.201.47.94 | egress-apex-13.serpwise.ai | Nuremberg, DE | | 195.201.47.124 | egress-apex-12.serpwise.ai | Nuremberg, DE | | 195.201.254.154 | egress-eu-central-1.serpwise.ai | Nuremberg, DE | ### Content analysis These fetch pages for SEO analysis (meta tags, image alt text, crawling) rather than serving visitors. They are on the same schedule as any other crawler and honour robots.txt, but they hit the same origin and the same blocking rules, so allowlist them too. | | | | |-----------------|-----------------------------|---------------| | 178.104.122.106 | edge-ai-service.serpwise.ai | Nuremberg, DE | ## Verifying these are really ours Every address has forward-confirmed reverse DNS: the reverse lookup returns a `serpwise.ai` hostname, and that hostname resolves back to the same address. Only whoever controls both the address and the domain can produce that pair, so it is safe to key an allowlist on. The same test Google publishes for verifying Googlebot. ``` dig -x 5.161.16.121 +short # → egress-us-east-4.serpwise.ai dig egress-us-east-4.serpwise.ai +short # → 5.161.16.121 ``` Names follow `egress--` for outbound origin fetches, `edge--` for node primaries, and `ingress-*` for addresses that only receive traffic and never appear in this list. ## Seeing your visitors' real IPs We forward the original visitor address on every origin request, so your logs and per-IP rate limiters do not have to count our proxy as one very busy client: - `X-Forwarded-For` - the visitor's IP - `X-Forwarded-Proto` - the visitor's scheme - `X-Forwarded-Host` - the hostname the visitor requested To restore them at the origin, trust this list in `mod_remoteip` (Apache), `ngx_http_realip_module` (Nginx), or your WAF's trusted-proxy setting. One honest caveat: this fixes limits that run *after* the request headers are read by Wordfence, fail2ban, ModSecurity, and application rate limits. A block that fires earlier, at the network layer or in an edge bot-challenge, never sees the header and still needs an explicit allowlist entry. ## Update policy This list is generated from the running gateway configuration rather than maintained by hand, and a check runs against the live fleet to catch any address in use that is missing here. It changes rarely. Addresses are added before they carry traffic and retired only after they have been idle. Poll [/ips.json](/ips.json) if you automate against it. Last updated 2026-08-14. ## Questions, or a block you need lifted Email [hello@serpwise.ai](mailto:hello@serpwise.ai). If you are investigating traffic from one of these addresses right now, include the address and a timestamp and we can tell you which site it was serving.