Website
HTTP Status Checker
Check status codes, redirects and response time.
Results appear here. Enter a URL with http:// or https://, then select Check status.
Domain Health Report
This page checks one thing. The report checks thirteen — and tells you what to fix first.
A one-off €14.90 report, delivered by email in minutes. Every finding comes with a concrete fix, prioritized.
- DNS records (A/AAAA)
- Nameservers (NS)
- Mail servers (MX)
- SPF record and policy
- DMARC record and policy
- DKIM record (common selectors)
- HTTPS availability
- HTTP to HTTPS redirect
- TLS certificate (issuer, validity, expiry)
- Security headers (HSTS, CSP…)
- CAA records
- robots.txt availability
- sitemap.xml availability
How the HTTP status check works
- Enter a full URL, such as https://example.com, and submit the form.
- The URL is sent to the FKINFAST server. A diagnostic HTTP client connects to the destination, follows redirects up to 5 hops and reads the response status.
- When a status is confirmed, the result shows the status code, redirect count, final URL and total time, plus a PASS, WARNING, FAIL or UNKNOWN classification.
Checks run from FKINFAST's server, not from your browser. The URL is not stored and no response body, response header or resolved IP address is returned to this page.
Result states
- PASS
- The server answered with a 2xx success status.
- WARNING
- The server answered with a redirect or a 3xx response that could not be completed, so no final status was read.
- FAIL
- The server answered with a 4xx client error or 5xx server error status.
- UNKNOWN
- No HTTP status was confirmed: the check timed out, the connection or TLS handshake failed, or the destination was rejected.
Page-level errors are separate from these results. A validation error, rate limit, busy response, unavailable service or network failure is shown as an error, not as a FAIL result.
URL rules and limits
- Only http:// and https:// URLs are accepted.
- Only the default ports are allowed: 80 for http and 443 for https. Custom ports are rejected.
- URLs containing credentials (user:password@) are rejected.
- Loopback, private, link-local, multicast and cloud metadata addresses are blocked before any connection is made.
- Redirects are followed, up to 5 hops. The whole check has a 15-second deadline.
- One URL is checked per request, limited to 10 checks per 60 seconds per client IP.
What the checker does not return
The checker is a diagnostic HTTP client, not a browser. It never returns the response body or response headers, never displays the resolved IP address, does not execute JavaScript and does not render the page. Query strings are omitted from the URLs shown in results.
HTTP status checker FAQ
Is the URL private?
No. The URL is sent to the FKINFAST server so the check can run there. FKINFAST does not store the URL or the result. Standard edge and server request metadata, such as time and source IP, may be retained by Cloudflare and the hosting provider as part of normal operation.
Why does a reachable website return UNKNOWN?
UNKNOWN means no HTTP status was confirmed: the DNS resolution, connection or TLS handshake failed or timed out, or the destination was rejected as private or otherwise unsafe. It is not a statement that the site is down, and it is not a FAIL.
Does this tool check whether my site is up?
No. It performs a single request from one server at one point in time. It is not continuous uptime monitoring and it says nothing about availability from other networks or regions.
Why can't I check a URL with a custom port?
Only the standard web ports 80 (http) and 443 (https) are allowed, so the checker cannot be used to probe arbitrary services. The restriction applies to the input URL and to every redirect.
Does the checker follow redirects?
Yes, up to 5 hops. The result shows how many redirects were followed and the final URL. If the chain exceeds the limit, the result is WARNING, not a hard failure. Query strings are omitted from shown URLs.