Broken Link Checker
AvailableFind broken links: crawl a page or a small part of a site and check every link and resource for 404s, server errors, timeouts and redirects.
Find broken links
Link report
Sample data, design preview. These results are made up, using example.com addresses, to show the layout. No request was sent and nothing here is a real measurement.
Working…
Enter a URL to check its links for 404s, server errors and redirects.
How it works
The NetTools server downloads the start page, extracts its links, checks each link with a lightweight request and, within the crawl scope you choose, follows links on the same host. Every link gets its status code, so 404s, server errors, timeouts and redirects stand out.
Result categories
- Broken: 404, 410 and other 4xx answers, or a domain that does not exist.
- Error: 5xx server errors, timeouts, TLS and connection failures. Often temporary; check again later.
- Blocked: 401, 403 or 429. The server refused the automated check; the page may work fine in a browser.
- Redirects: works, but via one or more redirects. Update the link to the final URL.
Safeguards & responsible use
- Crawls only the host of the start URL, with hard caps on pages (≤ 100), depth (≤ 3) and total requests; external links are checked with one request each.
- Polite crawling: limited concurrency per host, robots.txt respected for crawled pages, a clearly identified NetTools user agent.
- SSRF protection on every request; results are not stored.
Frequently asked questions
Why is a link reported as “Blocked” instead of broken?
Some servers answer automated requests with 403 or 429 even when the page works in a browser. Those are reported separately so they are not mistaken for broken links; check them manually.
Does it check links added by JavaScript?
No. Links are read from the HTML as delivered by the server; links created later by scripts are not found.
How large a site can it crawl?
Up to 100 pages per check, to keep the load on your server and ours reasonable.