WordPress allows plugins and themes to make HTTP requests to external domains. While this is necessary for many plugins and themes to function properly, it can also pose a security risk if not managed properly.

On the allow list

WordPressA plugin or theme calls out
Allow listWP_ACCESSIBLE_HOSTS
meowapps.comRequest goes through

Any other domain

WordPressA plugin or theme calls out
Allow listWP_ACCESSIBLE_HOSTS
Other hostsWP_HTTP_BLOCK_EXTERNAL stops it

The WP_HTTP_BLOCK_EXTERNAL constant

By default, WordPress lets plugins and themes call any external site. The WP_HTTP_BLOCK_EXTERNAL constant changes that: once it is set to true in your wp-config.php file, every external HTTP request is blocked, except the ones to your own site and to localhost.

define( 'WP_HTTP_BLOCK_EXTERNAL', true );

Careful: this also stops WordPress itself from reaching api.wordpress.org, so updates for WordPress, plugins and themes stop working until you allow it again, as shown below.

Let’s allow specific hosts (domain names)

To let some domains through, list them in the WP_ACCESSIBLE_HOSTS constant, right below the first one. It takes a comma separated list, and wildcards work. For example, to keep WordPress updates working and let the Meow Apps plugins reach meowapps.com:

define( 'WP_ACCESSIBLE_HOSTS', 'api.wordpress.org,*.wordpress.org,meowapps.com' );

One entry covers all your Meow Apps plugins. If other plugins or themes need other domains (for example api.openai.com when AI Engine uses OpenAI), add them to the same list. Anything that isn’t on it stays blocked.