HTTP(S) Check

Hit any URL from 5-10 global probes and see per-probe HTTP status code, response time, and full timing breakdown (DNS / TCP / TLS / first byte / download). Useful for uptime snapshots, CDN verification, and regional availability checks.

Tool Networking Updated Apr 20, 2026
X Facebook LinkedIn Reddit Email
How to Use
  1. Enter a URL or host (e.g. https://example.com, github.com).
  2. Pick HEAD or GET. HEAD is faster and polite; GET pulls the full body.
  3. Each probe reports status code, total time, and timing phases.
URL
HTTP request issued from globalping.io probes. Free, no signup.
Try:
Per-probe response

Enter a URL above — status code + timing breakdown from every probe lands here.

What you see

Status code
HTTP response code (200 / 301 / 404 / 5xx ...)
Total time
Full request-to-response duration
Phases
DNS / TCP / TLS / TTFB breakdown per probe
Regional split
Spot geo-specific redirects or blocks

Frequently Asked Questions

What do the timing phases mean?

DNS = name resolution, TCP = handshake, TLS = certificate + cipher negotiation, First byte = time to first response byte (includes server processing), Download = content transfer.

Why does one probe show a different status code?

Geo-based redirects, A/B tests routed by GeoDNS, CDN cache variance, or regional rate limits.

Common Use Cases

Uptime snapshot

One look tells you if a URL is reachable everywhere or only from some regions.

CDN health check

Compare TTFB between probes — a good CDN is fast from every continent.

Regional redirect audit

See what status code + final URL each region is hitting.

Last updated: