301 vs 302 redirects

Redirects 301 and 302 occur at the application layer, so distinguish network reachability from the web-server response. DNS can resolve, TCP/TLS can connect, and HTTP can still return a redirect or error. Status code, Location, hostname, path and URL scheme describe different parts of the transaction.

How to investigate the web response

Check DNS, then TLS and the HTTP response without hiding the redirect chain. Compare the requested hostname with the actual target URL. A 4xx response generally describes the request or access, while 5xx indicates unsuccessful server-side handling, although a reverse proxy or CDN may be another participant in the path.

The detail that matters

A 301 communicates a permanent redirect intention while 302 is temporary semantics in common web use. Inspect the Location header and the entire redirect chain; loops and unnecessary hops add latency, and cached permanent redirects can make testing confusing after configuration changes. For an external check of the site, use 2ip site information check.