This page provides some technical information and guidelines about using our products for network administrators, server admins, and web hosts. By following these guidelines, you’ll help ensure that our shared user base has the best experience!
The following range needs to be fully whitelisted:
From Address To Address 220.127.116.11 18.104.22.168 CIDR Notation For WordFence use this 192.0.[64-127].[1-254]
If you are using Sucuri or Cloudflare please open a support ticket with us so we can send you the ranges in the format they use.
In order for a blog or forum to use Akismet to check spam, it needs to be able to make outgoing TCP connections to servers at Akismet.com. If your network normally blocks outgoing connections from your public web servers, you’ll need to add a firewall rule permitting connections to Akismet.
If your security filters allow exceptions based on hostnames, you should permit connections on port 80 to:
Most Akismet API calls will be made to a host name of the form
api_key.rest.akismet.com, where api_key is an alphanumeric string that is different for each web site owner.
22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11
All API calls are made on port 80 by default. If you are creating IP-based rules, it’s important that you allow connections to all of the listed IP addresses.
Important: these IP addresses are current as of 2016-01-27, but are subject to change.
Akismet Specific System Requirements
Akismet is a spam filtering service. It’s most commonly used with WordPress, but is often used with other blog platforms, forum applications, contact forms and similar web apps. It’s a centralized service, so TCP connectivity to servers at Akismet.com is required for it to work.
System requirements for the WordPress plugin are the same as for WordPress, plus:
gethostbynamelfunctions must not be disabled (they are enabled by default in PHP)
- TCP connectivity to akismet.com
System requirements for other Akismet plugins and implementations vary, but TCP connectivity is always required.
Here are helpful Jetpack troubleshooting links particularly relevant for hosting providers:
- Debug a site – https://jetpack.com/support/debug
- Error messages deciphered – https://jetpack.com/faq-errors
- Troubleshooting tips – https://jetpack.com/faq-troubleshoot
- Known issues – https://jetpack.com/faq-issues
- Common WordPress errors – https://codex.wordpress.org/Common_WordPress_Errors
- Support docs – https://jetpack.com/support
- Help forums – https://wordpress.org/support/plugin/jetpack
Download a printable .pdf of these Jetpack links.
Jetpack Specific System Requirements
Read more about Jetpack’s Server Requirements. Don’t worry—it is virtually the same as what WordPress expects.
Whitelist all communications between WordPress.com and Jetpack
Jetpack, much like other plugins, services, and apps like the mobile apps, relies on the XML-RPC file to communicate with WordPress.com.
If you’d prefer to use a whitelist, you’ll need to whitelist those IP ranges:
- 18.104.22.168-22.214.171.124 (in CIDR notation 126.96.36.199/20)
- 188.8.131.52-184.108.40.206 (in CIDR notation 220.127.116.11/20)
- 18.104.22.168-22.214.171.124 (in CIDR notation 126.96.36.199/20)
- 188.8.131.52-184.108.40.206 (in CIDR notation 220.127.116.11/22)
Important: these IP addresses are current as of 2019-03-15, but are subject to change. If you are writing IP-based firewall rules, you’ll need to update those rules any time the addresses change.