Scanned Oct 12, 2026, 5:41 AM UTC Markdown

Evidence report

Heritage Cars stack

heritagecars.online

A record of technologies visible in the site, vendors named in its public subprocessors list, and infrastructure published in DNS.

heritagecars.online

13 seen in the page · 0 named in their DPA · 1 in DNS · 802 ms

Heritage Cars is listed

Seen in the page

HTML, headers, cookies and bundles

Analytics

Google Analytics— loaded a script from its domain95%

Backend platform

Supabase— named inside a JavaScript bundle75%

Build tool

Vite— served a file from its own path90%

Feed

RSS— matched a marker in the page HTML80%

Font

Google Fonts— matched a marker in the page HTML80%

JS framework

React— named inside a JavaScript bundle75%

JS library

TanStack Query— named inside a JavaScript bundle75%

Metadata

Open Graph— declared in a meta tag95%

PaaS

Vercel— sent in a response header95%

UI framework

Radix UI— named inside a JavaScript bundle75%
shadcn/ui— named inside a JavaScript bundle75%
Tailwind CSS— named inside a JavaScript bundle75%

UI library

Lucide— named inside a JavaScript bundle75%

Named in their DPA

Read from the company’s own sub-processor list

No sub-processor list found. Most sites that sell to businesses publish one; a site that does not is simply quiet about its vendors, which is not the same as having none.

Published in their DNS

Anyone can check these with dig

Hostinger DNSDNSNS ns1.dns-parking.com

Everything above carries the signal it was read from. We do not guess: a tool we cannot point at is not listed, which is why this result may be shorter than scanners that fill the gaps.