HTTP

HTTP Test

Follow up to five redirects and measure each response time. Only HTTP/HTTPS URLs pointing to public hosts are allowed.

LEARN

Understanding HTTP status and redirects

HTTP Test requests a public HTTP or HTTPS URL, records the response status and follows a limited redirect chain. This is useful for checking whether a page responds, where a redirect points and how long each step takes from the OCS Ping server.

The checker is intentionally limited to public destinations and validates redirect targets as part of the safety rules for public destinations. A successful HTTP response does not guarantee that every page feature or client-side script is working correctly.

FAQ

Common questions

What is the difference between 301 and 302?

Both redirect the client, but 301 communicates a permanent move while 302 is generally used for a temporary redirect.

Why does a URL work in my browser but fail here?

The site may treat server locations, IP addresses, user agents, firewall rules or automated requests differently.

Does response time equal full page load time?

No. It measures the server-side request path used by this checker, not the complete browser rendering of all page assets.