
For developers and auditors inventorying destinations in a snippet before a migration, rewrite or content review.
Collect every unique link from an HTML fragment, resolve relative paths and leave with a clean destination list ready for review.
The sample includes a base address, an absolute link, a relative link, and a duplicate. After extraction, check that the list keeps only one entry per destination and that the relative path was resolved correctly.
Input
https://example.com/page
<a href="/contact">Contact</a> <a href="https://example.com/help">Help</a> <a href="/contact">Contact</a>Output
https://example.com/contact
https://example.com/helpThe extraction happens entirely in your browser. The HTML and base address you paste or import stay on your device and are not sent to any remote service. That makes it practical to audit a snippet without publishing it or creating an account.
No. It only extracts destinations from the HTML fragment. To learn whether a page responds, test the addresses separately with a link checker or a manual browser visit.
The fragment may rely on JavaScript to build links, or the href may be hidden in an attribute the tool does not treat as a link. Check the raw HTML and include the relevant markup in the input.
Provide a base address that matches the original page. The tool uses it to turn relative paths into complete addresses, which makes migration or audit comparisons much clearer.