Skip to content
Contact us
  • There are no suggestions because the search field is empty.

IP Addresses

Allow Prerender.io's IP addresses in your firewall or CDN settings to ensure uninterrupted crawling and rendering.

Summary/Overview

Prerender.io uses a static range of public IP addresses for its rendering and crawling infrastructure. If your site uses a firewall or restricts access at the network level (e.g., via a WAF or CDN), you must allow these IPs. This ensures Prerender bots can crawl and render your content for search engines.

You can view a regularly updated list of IP ranges here, or use the static ranges below as a starting point.

 

Detailed Explanation / How It Works

Primary IP Ranges

These static IP ranges are exclusively used by Prerender.io:

103.207.40.0/22
104.224.12.0/22
2602:2dd::/36

These ranges cover IPv4 and IPv6 traffic and should be whitelisted in your firewall or network configuration.

Alternative Narrow Ranges (/24)

Some services do not accept wide CIDR ranges like /22. If you're limited to using /8, /16, or /24 only, use the following narrower ranges:

104.224.12.0/24
104.224.13.0/24
104.224.14.0/24
104.224.15.0/24
103.207.40.0/24
103.207.41.0/24
103.207.42.0/24
103.207.43.0/24

Dynamic Considerations

The published IP list does update from time to time. For this reason, we recommend:

Ingress vs. Egress IPs

The ranges above are used by the rendering cluster (egress IPs). Our ingress addresses—such as those used by the Sitemap Crawler—may be different.

Specifically, the Sitemap Crawler uses the IP range 5.161.0.0/16, so make sure this is also allowed in your firewall or access control configuration if you're using sitemap-based recaching or crawl support.

To safely allow this crawler, permit access via user-agent string:

Prerender (+https://github.com/prerender/prerender)

 

Additional Context

IPv6 Support and Happy Eyeballs

Prerender will begin using RFC6555 Happy Eyeballs starting July 1, 2024. If your infrastructure supports IPv6, we will prefer those addresses. This improves connection time by simultaneously attempting both IPv4 and IPv6.

Traffic Origin & Server Regions

Prerender runs its infrastructure across US and EU regions. Paid customers can request rendering only from US-based servers if you want to restrict IPv6 or international traffic.

Common Pitfalls / Tips

  • Whitelist both the egress IPs and the sitemap crawler user agent string.
  • Some firewalls may block IPv6 by default — if you're experiencing render issues, check dual-stack support.
  • If needed, use the narrower /24 ranges when larger CIDR blocks can’t be configured.

Related Articles