Skip to content

Broken Link Checker

Extracts up to 100 links from a page, or takes a pasted list, and checks each in parallel — status, redirect target and response time, HEAD first and GET when refused.

Takes the links out of a page — or a list you paste — and asks each one what it answers with, four at a time. Broken links on a site that has been running for years are rarely where anyone expects, and the only way to know is to ask every one of them.

☁️ Uses our serverlinkshttpauditbatch

Our server makes this request for you. Only the page URL, or the list of URLs is sent to it — none of your cookies or login state goes along. The server will only connect to public addresses and refuses private and internal ones.

Up to 100 <a href> links are taken from the page and asked four at a time. HEAD first; servers that refuse it are asked again with GET.

How to use it

  1. Choose a page or a list

    Given a page, the <a href> links are extracted and checked. Given a list, one URL per line is checked as typed.

  2. Filter to the problems

    The "problems only" view hides everything that answered normally. Redirects are shown as a problem worth reading rather than an error — an old link that still works today is a link that will break later.

  3. Read the method column on odd results

    Each link is asked with HEAD first and re-asked with GET when a server refuses that. A row that only worked on GET is a server with a quirk, not a broken link.

Common questions

Why do some links come back 403?

Plenty of sites block anything that does not look like a browser, and some block datacentre addresses outright. A 403 here often means the link is fine for a person and refused for us — check it by hand before deleting it.

It only checked part of the page’s links

There is a cap on how many are extracted and a time limit on the whole run, so a large page is sampled rather than exhausted. For a full sweep, paste the list in batches.

A link marked private address is not broken

It was not checked at all. The outbound fetcher refuses private, loopback and link-local destinations, so a link to an intranet host is reported as skipped rather than tested. It may work perfectly from inside.

Does it follow links to other pages?

No. One page’s links, checked once. It is a link checker, not a crawler — which is also why it cannot be pointed at a site to walk it.

Feed it from

Next

These accept what this tool produces, so the result can go straight in.