Loading… · Yükleniyor…
1 redirect before the final page
The chain could not be followed to the end.
LiveSource: Direct HTTPS request (headers + first 64 KB of HTML)Observed:
Results are fetched live. DNS answers may come from a resolver cache for up to the TTL shown.
What this service recorded for this name on earlier checks. A check happens only when someone opens a report or calls the API: nothing is scheduled, so gaps between checks are normal.
23 checks since Sep 26, 2026, the latest on Oct 12, 2026.
No change in the recorded values across 23 checks.
The check starts at https://your-domain/ and follows Location headers for up to five hops, recording the status code and destination of each. If HTTPS does not answer at all, it starts from plain HTTP instead and says so. Redirects that point at private or internal addresses are not followed.
Only HTTP redirects are traced. A redirect done with JavaScript or a meta refresh tag happens inside the browser after the page has loaded, and does not appear here.
The history is kept for the domain name only; nothing about who looked it up is stored. Entries not seen again for 400 days are deleted. Changing A, AAAA and hosting values are normal for sites behind load balancers or content delivery networks.
Fixed points of reference, not rankings. Each line says what the value is compared with and where it came from.