Network Diagnostics and More
Checking test service
Menu
Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.

Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.

Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.

← All tool guides

Technical diagnostics

Website Accessibility and Path Tester guide

Check whether a public website resolves and responds, follow redirects and request optional community-probe HTTP and traceroute evidence.

Open Website Accessibility and Path Tester

What you need

  • Public HTTP or HTTPS website address
  • Optional multi-location check

How to use it

  1. 1Enter the full website address.
  2. 2Leave multi-location enabled when regional evidence is useful.
  3. 3Run the test.
  4. 4Review DNS, each redirect hop and the separate community-probe results.

Understanding the results

  • A reached result means the hosted checker received an HTTP response; it does not prove every user can access the site.
  • Different community paths can indicate regional routing or filtering differences.

Recommended next actions

  • Repeat from the affected network and correlate with DNS, TLS and service-owner logs.

Common problems

  • Community probes can be busy or rate-limited.
  • A site may block automated HEAD or range requests while working in a browser.

Privacy and security

  • The public target is sent to the hosted service and, when selected, to Globalping community probes.

Worked example

Scenario
A customer portal will not load
Example input
https://portal.example.com/login with multi-location enabled
How to read it
DNS succeeds and redirects reach HTTP 200 in two regions, while one traceroute times out; investigate regional routing without treating the timeout alone as proof of an outage.

Limitations

  • The path does not originate from the user's device and volunteer probe availability is not guaranteed.

Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.