website crash checker
Website Crash Checker: Is Your Website Down?
Enter any public URL and check whether the website is down or crashing. IsItCrashing discovers internal pages, checks each one for errors, and returns a focused list of what broke and why.
Free first-pass scan
Check your website for broken pages
Paste a public URL into IsItCrashing and scan discovered pages for failed responses, blank pages, broken assets, and website health issues.
Quick answer
IsItCrashing is a free website crash checker. Enter a public URL and the scanner discovers internal pages from your sitemap and links, then checks each page for HTTP errors, blank responses, broken assets, and JavaScript crashes. You get a focused report of which pages failed and why.
What a website crash checker does
A website crash checker scans your site's public pages and reports which ones are returning errors, loading blank, serving broken assets, or crashing at the browser level. Unlike a basic ping or uptime check that only tests your homepage, IsItCrashing discovers internal pages from your sitemap and links then checks each one.
This makes it practical for catching post-deployment regressions, broken redirects, CMS publishing failures, and route-level crashes that a single-URL checker would never surface.
What the crash checker looks for
- HTTP 404 Not Found errors on discovered internal pages.
- HTTP 500 and other server-level errors that indicate a backend crash.
- Blank pages where a route responds with 200 but renders no visible content.
- Broken critical assets including JavaScript bundles, stylesheets, and preload files.
- Redirect loops and network failures that prevent a page from loading.
- Important frontend JavaScript crashes on browser-checked pages when browser scanning is configured.
When to run a website crash check
The most common trigger is a deployment. After pushing code, running a migration, switching CDNs, or changing redirects, a crash check gives you an automated first-pass across your public pages before users find the problems.
Other common triggers include CMS content updates, campaign launches that add new landing pages, plugin or dependency updates, and client handoffs where you need a documented clean bill of health.
How it differs from Down Detector
Down Detector tracks crowd-sourced outage reports for major third-party services like Netflix, Twitter, and banks. It answers 'is this big service down for everyone?' using user-submitted data.
IsItCrashing checks your own website's internal pages using an automated crawler. It answers 'are my pages broken?' with specific URLs, error codes, and diagnostic details — not crowd reports. The two tools answer completely different questions.
How to use the crash report
After the scan completes, start with the Failed Pages section. Pages are sorted by severity: server errors first, then 404s, then blank pages, then broken assets. Fix the highest-traffic and highest-value paths first — checkout, signup, pricing, documentation, and pages linked from your main navigation.
The Inspect button on each failed row reveals the full diagnostic detail including status code, error type, and error message. Export the full report as a PDF to share with your team or include in a client handoff.
Crash checker vs uptime monitor
An uptime monitor tells you when your homepage goes down and alerts you after the fact. IsItCrashing lets you proactively scan all discovered public pages before users hit them — finding route-level crashes, blank pages, and broken assets that uptime monitors miss entirely.
FAQ
What is IsItCrashing?
IsItCrashing is a free website crash checker that lets you enter a public URL and scan discovered pages for broken pages, failed requests, blank pages, broken critical assets, and website health issues.
How long does a scan take?
Most scans complete in under a minute. The exact time depends on how many pages are discovered and how fast each page responds. A site with 60 pages typically scans in 20–45 seconds because pages are checked concurrently, not one by one.
How many pages does it scan?
The scanner discovers up to 60 internal pages per scan from your sitemap and internal links. It checks the most important pages first based on sitemap priority and crawl depth. Very large sites with hundreds of pages may need a dedicated crawl tool for full coverage.
How is it different from Down Detector?
Down Detector collects crowd-sourced outage reports for major third-party services like Netflix, Twitter, and banks. It tells you whether a big public service is down for everyone. IsItCrashing scans your own website's internal pages using an automated crawler — it tells you which of your pages are broken and exactly why. They answer completely different questions.
Can I check my website after a deployment?
Yes, that is one of the most common use cases. After a deployment, migration, redirect change, or CMS update, paste your production URL into IsItCrashing and run a scan. You get a full report of working and failed pages in under a minute, so you can catch regressions before users do.
Is this the same as an uptime checker?
No. A basic uptime checker usually tests one URL and alerts you after your homepage goes down. IsItCrashing discovers internal pages and reports specific failed pages, blank responses, broken critical assets, and browser crashes when browser checks are available — across all discovered URLs, not just one.
More answers in the full website crash checker FAQ.
Free first-pass scan
Check your website for broken pages
Paste a public URL into IsItCrashing and scan discovered pages for failed responses, blank pages, broken assets, and website health issues.