Available
The regional probe received a successful response or a valid HTTP redirect.
Check one URL from independent network probes to see where it loads, returns errors or is unreachable. Useful for investigating regional restrictions, VPN, CDN, DNS and firewall issues.
Results appear as probes respond.
| Location | Result | HTTP | Response | DNS / TTFB | IP and network | Detection details |
|---|
HTTP availability is checked from one available probe per country through the distributed Globalping network. The URL is sent to Globalping for measurement. Results may differ from those of a specific carrier, browser, VPN app or JavaScript protection system.
The regional probe received a successful response or a valid HTTP redirect.
The probe reached the website, but a WAF, CAPTCHA or anti-bot system rejected the automated request. This does not necessarily mean the website is broken.
Possible causes include DNS, routing, TLS, hosting, a firewall or regional network restrictions.
Answers about inputs, results and tool limitations.
The tool requests one URL through regional probes in the Globalping network. It shows successful responses, protection responses, errors and unavailable probes, together with status codes and timing details. Select at least two countries, start the check and wait for the probes to respond.
Compare the same URL across locations and repeat unexpected results before drawing conclusions. The URL is sent to Globalping for measurement. A probe does not reproduce a particular person's carrier, browser, VPN app or JavaScript protection state, so a regional result is evidence for investigation rather than proof of universal access or blocking.
A 403 response means the probe reached a server that refused the request. When protection indicators are detected, the report distinguishes this from receiving no HTTP response at all.
A WAF, CAPTCHA or anti-bot system can reject automation while allowing people using a browser. Review the evidence and compare with a normal visit before treating the result as downtime.
Your browser may have cookies, JavaScript verification or a different network reputation. The measurement probe makes an automated request from its own network and does not inherit your session.
Compare the URL, status and protection evidence. A protection response does not establish that the website is unavailable to everyone in that country.
Compare the same URL across multiple countries, then repeat the check. Look for consistent differences in status, DNS, connection errors or protection responses rather than relying on one isolated measurement.
Review CDN, WAF and provider rules alongside results from real users. One probe per country cannot represent every carrier or network in that country.
“No response” means a selected probe did not obtain a usable HTTP response. Possible causes include DNS, TLS, routing, hosting or firewall issues. “No probe” means no suitable measurement node was available; it does not prove the website is down.
“Checking” indicates that the measurement is still in progress. Wait for results or repeat later if a probe remains unavailable.
DNS time describes name resolution. TTFB measures the time until the first response byte, while total time describes the reported request duration. Compare values together with status and network details.
These are probe measurements, not a browser page-load or Core Web Vitals test. Geography, routing, caching and server behavior can change timings between runs.
The provider selects an available probe in each requested country. Probe availability and routing can change, and the next run may use a different city or network.
Website caching, protection and transient network conditions can also affect the response. Record probe details when comparing runs and repeat inconsistent measurements.
Review the reported protection evidence and verify the public page manually. If you manage the website, inspect the relevant WAF or anti-bot logs and rules to determine whether the rejection was expected.
Do not treat a blocked automated request as proof that human visitors cannot access the site. Compare real-user behavior and independent measurements before changing protection settings.
The requested URL is sent to the Globalping service for distributed measurement, including its path and query where applicable. Regional probes then contact the destination.
Use public URLs. Avoid links containing credentials, private access tokens, confidential documents or one-time secrets. The tool does not transfer your browser's authenticated session.
This check is free after sign-in and does not charge credits, including when a provider or network error occurs. You can run it again.
If the service is busy, a limit is reached or a probe is unavailable, wait and retry later. Repeating a request immediately may not resolve a temporary provider problem.