Tech stack
Framework, CMS or site builder, build tool, UI kit, hosting, CDN and third-party services, with versions.
Site DNA
Enter a website. We read its HTML, JavaScript bundles, CSS, font files, headers and DNS to show the framework, motion stack, typography, design tokens and infrastructure behind it.
About the Site DNA
Site DNA reads a website the way a browser does: its HTML, every JavaScript bundle, stylesheets, font files, headers and DNS. From those it identifies more than 230 technologies with versions and evidence, opens the font files to name the typeface and foundry, and extracts the design system.
Framework, CMS or site builder, build tool, UI kit, hosting, CDN and third-party services, with versions.
GSAP, Framer Motion, Lenis, three.js and WebGL, page transitions, and whether reduced motion is respected.
Every typeface with weights, foundry, designer, license and the writing systems it covers.
Color palette with variable names, type scale, fluid type, radii, breakpoints and dark mode.
Any public address, or paste a page's source if the site blocks automated visitors.
HTML, up to about 48 scripts, stylesheets, font files, source maps, headers and DNS. Nothing is executed.
Run a deep scan to render the page in a real browser for live versions, WebGL and Web Vitals, or compare two sites.
Enter the site in Site DNA. It identifies the framework, CMS, hosting and libraries from the site's own files, and shows the evidence for each, like the file and the matched code.
Site DNA opens the site's font files and reads the real family name, foundry, designer and license, along with every weight the site loads and where the font comes from (Google Fonts, Adobe Fonts or self-hosted).
Yes, for single sites: it detects technologies with versions and evidence, and adds what those tools don't show, such as fonts from their files, design tokens, motion libraries and a real-browser deep scan.
Yes. Compare puts two sites side by side: their stacks, motion, typefaces and palettes.