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

Evidence report

CommentHunter stack

commenthunter.click

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

commenthunter.click

16 seen in the page · 5 named in their DPA · 2 in DNS · 799 ms

CommentHunter is listed

Seen in the page

HTML, headers, cookies and bundles

Advertising

Google Ads— loaded a script from its domain95%

Analytics

Datafast— loaded a script from its domain95%
Google Analytics— matched a marker in the page HTML80%
Plausible— loaded a script from its domain95%

Backend platform

Supabase— named inside a JavaScript bundle75%

Build tool

Vite— served a file from its own path90%

JS framework

React— named inside a JavaScript bundle75%

JS library

core-js— named inside a JavaScript bundle75%

Live chat

Crisp— matched a marker in the page HTML80%

Metadata

Open Graph— declared in a meta tag95%

PaaS

Vercel— sent in a response header95%

Tag manager

Google Tag Manager— matched a marker in the page HTML80%

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

Google Analyticsanalytics source
“Analytics and advertising measurement identifiers (for example Google Analytics / Google Ads tags, or similar tools when enabled) to understand product usage and measure campaigns”
Supabasedatabase source
“Supabase — authentication, database, storage, and edge functions”
Resendemail source
“Resend (or similar) — transactional and marketing email delivery”
Vercelhosting source
“Hosting / CDN (for example Vercel) — to serve the website”
Stripepayments source
“If you purchase a plan or credits, payment processing is handled by Stripe. We may receive and store billing-related identifiers such as Stripe customer ID, subscription status, in”

Published in their DNS

Anyone can check these with dig

VercelHostingCNAME cf144776a924adaf.vercel-dns-017.com
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.