A clearer view of your website

See how one public URL responds: HTTP status, HTTPS, redirects and selected headers, in one server-side HEAD snapshot.

One URL. Observed responses. No health score.

Start with a URL

What would you like to check?

HEAD only

Include http:// or https:// and a public hostname on its standard port. Credentials, IP addresses, internal names and reserved example.com/net/org destinations are not accepted. Browser-only fragments are removed.

Before you check: the full URL, path and query values are sent to Roled's server and the target website. The target sees Roled's server; hosting, resolver and target logs may record the request. Do not submit sensitive URLs.

Up to five redirects. No automatic requests or retries. Reset or edits ignore old results; they may not stop server work.

Your snapshot starts here

Check a URL to see what responded, how it connected and what is worth a closer look.

What this check can and cannot tell you

One bounded HEAD snapshot from Roled's server, using public IPv4. HEAD may differ from browser GET, cookies, location and transient load. No GET fallback, page body/HTML inspection, rendering or continuous uptime measurement.

Timing is the sum of observed HEAD requests, not browser page load time or Core Web Vitals. Manual DNS, failed attempts and total endpoint time are excluded. Native DNS can block according to resolver settings and cannot be interrupted by elapsed-work checks.

This is not a complete security, SEO or accessibility audit. Verified HTTPS does not inspect certificate expiry, all protocols, ciphers or preload membership. HTTPS-only input does not test HTTP upgrade. Header presence does not establish effective browser policy, cache hits, freshness or total page size.

HTTP 403/429 may reflect target access policy; 405/501 may restrict HEAD. Network, DNS and TLS failures do not prove universal unavailability. Intermediate headers and published destinations are identified in the results.

The tool saves no URL or report history in Drupal or browser storage. Admission records and hosting/resolver/target logs are separate. Page exit clears held UI state without promising secure memory erasure. Clipboard writes already started cannot be recalled. Full-value copying never changes the URL sent for inspection.