My site is broken
Start with the website setup report. If your public site and origin disagree, compare both endpoints using your server IP. Origin checks require domain verification.
These choices, favorites and recent tools stay in this browser. Private diagnostic jobs store encrypted inputs and reports for up to 24 hours. Data and retention details
53 free tools for people who run websites
Start with a website setup check. Save a private project when you want to repeat release checks or investigate a broken page after a change.
Verify a website you manage, save the responses you expect and compare private evidence across manual runs. Open Website projects to select or add a website.
Open website projectsKeep DNS, HTTPS and expected response content with a bounded history.
Check public pages and browser steps against a baseline you have reviewed.
Review failed scripts, browser errors and missing rendered content.
Choose a focused check, review its evidence, then repeat the same measurement after a change.
Start with the website setup report. If your public site and origin disagree, compare both endpoints using your server IP. Origin checks require domain verification.
Measure a public page with one screen size and inspect its requests and rendering. If you already have a HAR capture, analyze it locally instead.
Compare the current site with the proposed server before changing DNS. Supply the new public server IP, verify the domain and state the responses you expect.
Save a checklist in a verified website project, run it manually and compare with an approved baseline. For a single report, use the visual comparison or journey tool.
Check the site from our server, then look at what your own connection can reach.
Record failed scripts, browser errors and visible content on a verified project page. Compare completed evidence after changing the deployment.
Focused checks for setup, hosting moves, performance and releases.
See the A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records for any domain.
Check a certificate's expiry, covered names, chain and supported TLS versions.
Follow a URL through every redirect and spot loops, HTTP downgrades and long chains.
Compare the current site with a proposed server before changing DNS.
Repeat a browser measurement and inspect timing, requests and rendering evidence.
Compare two rendered pages and inspect screenshots and their pixel differences.
Step-by-step fixes for common problems, each linked to the tool that confirms it worked.
Warnings say what is wrong, why it matters and what to change, with config you can copy.
Run any tool without signing up. Generators and the header analyzer work entirely in your browser.
Related tools and guides help you investigate the evidence. Review the target and settings before each run.