How to use this check
Enter a public HTTP or HTTPS URL to run one point-in-time request through the SitePulse probe guard.
SitePulse normalizes the URL, blocks private/reserved destinations, resolves public addresses and performs a short HTTP GET.
Availability
Live one-shot probeCheck whether a public page answers with a healthy HTTP status and bounded timing data.
The result shows final status, response class, content type and bounded timing notes.
Enter a public HTTP or HTTPS URL to run one point-in-time request through the SitePulse probe guard.
The result shows final status, response class, content type and bounded timing notes.
Support
Use the result first. Support and promotional areas stay separate from the useful result.
Enter a public HTTP or HTTPS URL to run one point-in-time request through the SitePulse probe guard.
SitePulse normalizes the URL, blocks private/reserved destinations, resolves public addresses and performs a short HTTP GET.
A 2xx or expected 3xx result is usually healthy; 4xx, 5xx, timeout or blocked redirects need investigation.
If https://example.com returns 200 with text/html, the public web route is reachable from the probe runtime.
A site can work in a browser but fail from an external probe because of WAF, geo rules, DNS drift or TLS policy.
Compare DNS, CDN, WAF and origin logs before changing application code.
This is not uptime monitoring. It is a single web request from one runtime with short timeouts.
No. Monitoring, alerts and history belong to Account features.
No. Private, local, metadata and reserved destinations are blocked.