HTTP Response

How the server responds to requests

What is HTTP Response?

When you visit a website, your browser sends an HTTP request to the server, and the server sends back an HTTP response. This response includes a status code (like 200 for success, 301 for redirect, or 404 for not found) and various headers.

We check how the server responds to requests, including whether it redirects you to a different URL, whether HTTPS is enforced, and what the final destination is.

Understanding Redirects

A redirect is when the server tells your browser to go to a different URL. This is completely normal, but certain patterns warrant attention:

  • HTTP to HTTPS: Good. The site is upgrading your connection to be secure
  • Same-host redirects: Normal. Often used for www/non-www normalization
  • Cross-host redirects: Could indicate domain parking, acquisition, or potentially deceptive URLs
  • Redirect loops: The site is misconfigured and can't be reached
  • HTTPS to HTTP: Concerning. The site is downgrading to an insecure connection

How to Interpret This Signal

Positive

HTTPS enforced, no cross-host redirects

Attention

Redirects to a different domain

Warning

Redirect loop or HTTPS downgrade

Example Domains

See this signal in action:

google.com github.com bit.ly

Related Signals

HTTPS Security TLS Certificate
Check a Domain