Toolbox
Use these tools to diagnose outages, DNS issues, TLS and security-policy failures, crawl/indexing problems, redirect behavior, browser differences, and route-level access problems without setup.
Each tool is focused on a specific question, so support teams can move from "it is broken" to actionable evidence in a few minutes.
Pick the check that matches your incident stage: reachability, DNS, TLS trust, security policy, crawl control, HTTP behavior, client behavior, or network identity.
Check if a site is down for everyone or only your location, with multi-region probes and verdict classification.
Get your public IPv4 and IPv6, ASN, ISP, and geolocation context to debug routing and geo-based issues.
Inspect A, AAAA, CNAME, MX, NS, and TXT records to validate domain routing and mail configuration.
Guide: DNS Outage Troubleshooting · Comparison: DNS Lookup Tools
Validate certificate expiry, hostname match, issuer details, and TLS protocol so trust-layer failures do not get mistaken for full downtime.
Audit HSTS, CSP, frame, MIME, and browser isolation headers to spot missing protections and policy drift after deploys.
Check robots.txt availability, crawler directives, and sitemap declarations so indexing and crawl control issues are visible immediately.
Verify whether llms.txt exists, inspect a clean preview, and export structured output for AI documentation QA workflows.
Capture browser and device environment details for QA, compatibility investigations, and reproducibility.
Guide: Intermittent Outage Investigation · Comparison: User-Agent Tools
See what status codes are returned across regions and whether the response indicates success, error, or mixed behavior.
Guide: HTTP Status Codes Explained · Comparison: HTTP Status Tools
Check whether a domain redirects consistently to the expected final URL across multiple regions.
Guide: HTTP 301 Redirects Explained · Comparison: Redirect Checker Tools
A practical sequence for support and operations teams handling real incidents.
Start with the Website Down Checker to confirm whether the problem is global, regional, or specific to one route. Use this outage verification guide if you need a fast checklist.
If signals are inconsistent, run DNS Lookup to confirm A/AAAA and CNAME behavior before touching app-level fixes. Follow the DNS outage troubleshooting guide for deeper validation.
Use HTTP Status Checker and Redirect Checker to understand whether users hit the right endpoint and get healthy responses. Keep the HTTP status code guide open while triaging.
Run SSL Checker and Security Headers Checker to confirm certificate trust and response hardening. This helps separate browser trust failures from origin downtime and catches deploy regressions early.
When only some users are impacted, use IP and User-Agent checkers to isolate ISP, routing, and browser-specific causes. The intermittent outage guide helps structure the investigation.
If traffic and indexing reports change unexpectedly, run robots.txt Checker for crawl directives and the llms.txt Checker for AI discovery guidance.
Yes. These tools are free for normal usage and designed to give fast diagnostics without setup friction.
Start with the Website Down Checker. Then move to DNS, HTTP, and redirect checks for routing behavior. Add SSL and Security Headers checks when browser trust or policy issues are suspected, and use robots.txt plus llms.txt checks when discovery visibility changes.
Yes. The tools are structured for support handoffs: clear fields, copy-friendly outputs, and links to explainers so non-specialists can follow the diagnosis.
No. They are rapid diagnostics tools. For production monitoring, pair them with alerting, logs, and synthetic checks in your stack.
