To find which WordPress component contacts an outside domain, first identify the traffic class: a server-side request made by WordPress/PHP, or a browser request for JavaScript, CSS, images, fonts, or other assets. Use WordPress Site Health to check whether outbound HTTP requests are being blocked, then use a logger or browser developer tools that can observe the specific path. No single check or plugin documented here records every kind of third-party request.
What counts as a third-party request?
The phrase covers two different observation problems:
- Server-side WordPress/PHP traffic: WordPress, a plugin, a theme, or a scheduled task sends an HTTP request from the server. The response is handled by PHP, so it may not appear in the visitor’s browser network panel.
- Browser traffic: A visitor’s browser fetches a script, stylesheet, image, font, iframe, beacon, or similar resource from another domain while rendering a page. This can happen even when WordPress itself makes no outbound HTTP API call.
The HTTP Requests Manager listing explicitly warns that its logger concerns the first category and does not track browser asset loading. It also excludes several PHP networking mechanisms, so treat its results as partial visibility rather than a complete inventory.
Start with WordPress Site Health
In the dashboard, open Tools > Site Health and review the HTTP-request status. WordPress uses this check to report whether external HTTP API requests are blocked by WP_HTTP_BLOCK_EXTERNAL and whether permitted hosts are configured. See the WordPress Site Health screen documentation and the developer reference for WP_Site_Health::get_test_http_requests().
#1 Best Overall
This is a configuration and connectivity diagnostic. It is not a historical list of domains, and it does not identify the plugin or PHP call that initiated an individual request. A passing check therefore does not prove that no third-party requests occur.
Log server-side requests made through WP_Http
What HTTP Requests Manager says it records
The WordPress.org listing for HTTP Requests Manager says it can log requests made through WordPress’s WP_Http class and group them by URL, domain, page, page type, plugin, response status, and other fields. The listing also describes request timing and configuration for limits and timeouts.
“Plugin only detects and manages requests made using WP_Http class.”
That statement is the key coverage boundary. The listing names WP_Http_Curl and PHP functions such as curl_exec, fsockopen, and file_get_contents among mechanisms it does not detect. It also does not observe resources loaded directly by a visitor’s browser. The features and compatibility described on the listing can change; they are listing claims, not an independent performance or completeness test.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use the logger in the context where the request occurs
- Install and configure the logger only on a site where its stated WP_Http coverage matches the suspected code path.
- Reproduce the action: load the relevant front-end page, open the administration screen, run the plugin operation, or wait for the scheduled task.
- Filter or group the resulting entries by domain, URL, page or page type, plugin, status, and timing where those fields are available.
- Record the external host, request path, context, suspected component, response status, and duration. Repeat the observation in each context that matters; a front-end page load does not represent an admin screen or cron task.
A missing entry means only that the request was not observed through this logger’s documented path. It does not rule out browser traffic, non-WP_Http PHP calls, or lower-level network activity.
Inspect browser requests separately
For third-party scripts, stylesheets, images, fonts, iframes, analytics beacons, and similar resources, use the browser’s developer tools:
- Open the page in the browser and launch Developer Tools.
- Select the Network panel and enable recording before reloading the page.
- Inspect the Domain or request URL for hosts that differ from your site, then examine the initiator, resource type, status, and timing.
- Repeat with an authenticated session and on the specific admin screen if the unexpected traffic occurs in wp-admin.
This shows what the browser requested and which page code initiated it. It does not reveal a server-side PHP request that happened while WordPress rendered the page.
Compare the available diagnostic methods
| Method | Traffic coverage | Attribution detail | Timing | Best use |
|---|---|---|---|---|
| WordPress Site Health HTTP-request check | Checks the external HTTP API blocking configuration; not a request log | Reports blocking and allowed-host configuration, not a caller history | Not stated | Diagnose whether WP_HTTP_BLOCK_EXTERNAL or allowed-host settings are affecting requests |
| HTTP Requests Manager | Requests made through WP_Http; excludes browser assets and the mechanisms named in its listing |
Listing describes grouping by domain, URL, page, page type, plugin, status, and other fields | Listing describes request timing | Investigate WordPress/PHP calls that use the WP_Http path |
| Browser Network panel | Assets and other requests made by the visitor’s browser | Shows URL, resource type, initiator, status, and browser timing | Browser timing data | Find third-party front-end or wp-admin resources |
| External uptime or heartbeat monitor | Requests made by the monitoring service to a site or endpoint | Checks availability; does not identify the WordPress plugin or PHP call responsible for outbound traffic | Service-dependent | Confirm that a site or endpoint is reachable from outside |
For examples of an external monitoring plugin and the endpoints it can use, see the AVAR Server Monitor listing. Availability monitoring complements request tracing; it is not a substitute for local attribution.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteInvestigate requests the logger cannot see
Other PHP networking functions
If code uses cURL directly, sockets, stream functions, or another library instead of WP_Http, follow that code path with application or server-level instrumentation appropriate to your environment. The cited plugin listing does not establish a single tool that captures all of these mechanisms.
Rank #4
- Engineered with intuitives, this networking analyzers tool features militarys connectors and real time traffics visualization for networking diagnostics
- The integrated hardware acceleration chip ensures not packet loss during high bandwidth, making it essential for troubleshooting complex networking infrastructures
- Professional networking tool with precisions packet captures capabilities, builts using PCB and metal components for long in demanding environment
- for IT administrators, cybersecurity specialists, and networking engineers requiring advanceds protocols analysis for enterprises systems or lab configuration
- optimizes networking in servers room, automotive CAN bus systems, and IoTs environment with multiple protocols including TCPs, UDP, and HTTPs / HTTPS packet inspection
Requests from scheduled work
Run the observation while the scheduled event or queue worker executes. A normal page load may never trigger the outbound call. Record the event name, execution time, and component that owns the task.
Requests made outside PHP
Web-server modules, reverse proxies, operating-system jobs, container sidecars, and external services can generate network traffic independently of WordPress. Those require logs at the relevant infrastructure layer rather than a WordPress request logger.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use blocking controls only after mapping dependencies
WordPress documents WP_HTTP_BLOCK_EXTERNAL for blocking external HTTP API requests and WP_ACCESSIBLE_HOSTS for allowing specified hosts, including wildcard domains. The relevant references are the WP_Http class documentation and WordPress’s Site Health documentation.
Before enforcing a block, list every remote dependency you require: core and plugin updates, licensing checks, payment or fulfillment integrations, webhooks, translation services, telemetry, and other business-critical connections. WordPress warns that blocking external requests can interfere with plugin or core functionality. Apply changes in a staging environment or maintenance window, test the affected workflows, and keep a rollback path.
The http_request_host_is_external hook reference documents the hook’s purpose and signature. It does not by itself provide a complete, safe implementation for every installation, so treat custom filtering as code that requires testing against your site’s dependencies.
A repeatable investigation checklist
- Define whether the suspected traffic is server-side PHP, browser-side, scheduled, or infrastructure-level.
- Check Tools > Site Health for external-request blocking and allowed-host configuration.
- Use HTTP Requests Manager only when the suspected call uses
WP_Http. - Use the browser Network panel for scripts, styles, images, fonts, iframes, and beacons.
- For excluded PHP mechanisms, trace the responsible code or server layer with matching instrumentation.
- Capture the host, path, context, initiator or component, status, and timing where available.
- Repeat the check on the exact front-end, admin, cron, or plugin workflow that produces the request.
- Review dependencies before blocking hosts, then test and monitor the change.
The Bottom Line
Track WordPress/PHP calls and browser assets at different observation points: Site Health diagnoses blocking configuration, HTTP Requests Manager can expose WP_Http calls within its stated limits, and browser developer tools reveal client-side requests. Treat any one method as partial evidence, then verify the exact context before restricting a domain.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
