HTTP redirects

google.com redirect chain

https://google.com/ 2 hops 50ms

2 hops to https://www.google.com/

HTTP · 50ms · cross-origin

1s ago

What this means

The chain resolved cleanly. Each hop returned a valid 3xx with a Location header until the final destination. Pages with long redirect chains add latency to first-byte; consider collapsing them when possible.

Chain 2 hops · 50ms total

1 HEAD 301 https://google.com/ 17ms → https://www.google.com/

2 HEAD 200 https://www.google.com/ 19ms

Warnings

Chain crosses 2 hostnames (google.com → www.google.com). Cookies don't follow.

What to try next

Check final URL

Run /check/google.com for live multi-region HTTP status.

Inspect TLS

Look at the cert at /ssl/google.com — particularly important if the chain crosses origins.

DNS

/dns/google.com shows the records driving the start of the chain.

Methodology

Probe: We open a HEAD request to https://{host}/ and follow Location headers manually, capping at 10 hops. Each hop is independently SSRF-guarded — redirects that point at private IPs are blocked, not followed. Falls back to GET when a server rejects HEAD with 405.
Counts as DOWN: The first request fails entirely (DNS, TCP, TLS, or timeout). Nothing in the chain to inspect.
Counts as DEGRADED: Reserved for warning-only conditions: scheme downgrade (https→http) on an otherwise valid chain, cross-origin chain, or final URL that isn't HTTPS.
Detail: We do not execute JavaScript, honor meta refresh tags, or follow Refresh: response headers — only HTTP-layer 301 / 302 / 303 / 307 / 308 redirects. Body content isn't fetched on intermediate hops; the final hop uses GET if we hit the cap, otherwise HEAD throughout.
Cadence: Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
Rate-limited targets: If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
Data source: Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.