Footprint
Find the websites behind a brand.
I wanted to see what sits behind a company's main website. Its help centre, docs and other sites can sit elsewhere, and I can't count on links from the homepage to reach all of them.
Footprint starts with a domain and looks for those other sites, checking public certificate records and domain records and looking for the brand's name on hosted services. I check the matches. A name alone isn't enough for me to call it part of the company.
A small scan, from my own site. I saved it on 12 August 2026 and it found my main domain and its www address, both of which reached a working page. Two addresses. The saved scan records HTTP 200 for both, though www redirected to the main domain. That older scan didn't keep the redirect's own status in a separate column. The screenshot shows those saved rows in today's app.
What the scan keeps
I can see what answered. Each row keeps where the address came from, where a redirect ends and the title of the page that answered when the scan could read it. Footprint follows domain aliases to help me see which service sits behind a site.
It also reads the scripts a page loads because more addresses can be hidden in them. Sites within the brand's domains go in the main list. I can check outside services in a separate list if I need to trace what the page talks to. A site using a service doesn't tell me who owns it.
The list groups possible team sites, the main website and the kit behind it. I've got filters and an export of the rows on screen. If I've run a crawl, the graph shows the links it found. My saved scan has two sites and no link edges.
Wellington does the crawling
Footprint uses Wellington Crawler for the crawl. It uses Wellington again when the first checks can't get an answer. I've kept those jobs on the same engine, so a fix in Wellington can reach both.
Today I can read the response from the address I asked for and the page it sent me to in separate columns, with a status for each step along the way. I can read both.
Footprint also reads what a page and its headers tell search engines to do, and if it can't read those instructions, it leaves the answer unknown. My August scan didn't record them. I've left those cells blank.
Keeping the earlier scan
Completed scans save into a local history where I can open one later, look through it again or pick two to compare. The comparison shows sites that appeared, disappeared or changed between the saved scans. From files I've already got.
It doesn't run a fresh scan for the comparison. I'll still check how each scan ran before reading a missing site as a change at the company. A request that failed can leave a gap in the list.
I can't get a complete view from public records alone and I'll still need to check the labels Footprint puts on what it finds, even when a site answers and there's a full row in the table. I've got it running locally.