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

Evidence report

HumanText stack

humantext.click

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

humantext.click

18 seen in the page · 0 named in their DPA · 2 in DNS · 1200 ms

HumanText is listed

Seen in the page

HTML, headers, cookies and bundles

Analytics

Databuddy— matched a marker in the page HTML80%
Datafast— loaded a script from its domain95%
Mixpanel— matched a marker in the page HTML80%
Plausible— loaded a script from its domain95%
PostHog— named inside a JavaScript bundle75%
Snowplow— named inside a JavaScript bundle75%

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

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 EmailEmailMX mx1.hostinger.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.