link status
Every link on the page,
and what each one answered.
This reads the links a page declares and asks each one for its status. It stops at 50 links, and the first line of the report says how many it did not ask about — nothing here is called fine unless every link on the page was looked at.
This tool works differently from the generator. The generator never uploads your image — it runs in your browser. The checker cannot: it fetches the public address you type, from our server, and reads that page’s HTML, for the links it declares — the body is fetched and read here, then turned into findings and dropped: it is never stored, and never sent back. Each link it then asks about is asked for only the status and headers it answers with, and those bodies are cancelled unread. Up to fifty of them, on whatever servers the page points at, from one click. Only the address you enter is sent. The addresses you check are then kept in this browser, so it can tell you what changed since last time; they go nowhere, and you can clear them.
Questions
Why does it stop at fifty links?
Because one click here becomes one request per link, aimed at servers that did not ask for them. Fifty was measured rather than guessed: thirteen real pages — news, documentation, shop categories, blogs and corporate home pages — declared between 27 and 436 unique links, with a median of 137. Fifty clears the smallest of them, which is the least a limit can do and still ever read a page whole, and stops short of turning one click into a hundred outbound requests. When the limit bites, the report says how many links it did not ask about rather than quietly leaving them out.
Why is there no green tick when most of my links are fine?
Because a tick over a list nobody finished reading is the one answer a report like this must never give. If any link was not asked about — past the limit, or an address this server will not fetch — or if any link was asked and gave no answer, the verdict is “not measured” rather than a pass. Anything actually found broken is still reported.
A link works in my browser but says it gave no answer. Is it broken?
Not necessarily, and that is why the report does not call it broken. A request that did not complete is a measurement of our request, not of the page at the other end: a server can refuse anything that is not a browser, rate-limit a burst of requests, or have one bad moment on one network. Open it and see before changing anything.
Does it check links on the whole site?
No. One page, the one whose address you give. Crawling a site means storing what was found across many pages and deciding when to stop, and this tool does neither — it reads one page’s markup, asks its links for a status, and forgets both.
Can I check my link-in-bio page with it?
Yes — give it the page’s address. Linktree writes its links into the page as ordinary links, and on every Linktree page measured the owner’s links came first, so they are the ones asked about when the limit bites; the host’s own footer and profile links follow, because the page declares those too. Two things it can miss: video blocks, which on nearly every page measured were players rather than links, and any host that refuses requests that are not a browser — then the report says which status the page answered with instead of showing an empty list.