Domain & DNS

Site Info

Title, description, stack, and tech used on any site.

Website URL http or https (default https). Up to 3 redirects are followed; only the first 2 MB of HTML are analyzed.

Try: laravel.com github.com wordpress.org cloudflare.com

About this tool

Site Info fetches a website's landing page from our Frankfurt server and reports everything that page broadcasts about itself: the HTML <title>, the meta description, Open Graph and Twitter Card metadata, the favicon URL, the canonical URL, language hints, and a fingerprint of the underlying tech stack (server, CMS, frameworks, analytics, ad networks, CDN). The check uses a real browser-style HTTPS request — including following up to five redirects and reading HTTP/2 responses — so what you see is what a normal visitor would see.

Tech detection runs against signatures for ~1,500 products: server headers (nginx, cloudflare, litespeed), HTML markers (generator meta, framework-specific class names, asset paths), and JavaScript globals exposed on first render. Each detection is shown with a confidence level and the snippet that triggered the match. SSL/TLS details, the response chain (every redirect with its status code), and a render-time estimate are included in the same report.

When to use this tool

Competitive intelligence. See what CMS, framework, analytics, and ad network a competitor uses without poking around their DOM by hand.
SEO audits. Confirm title, description, Open Graph, canonical, and language tags are all present and correctly populated.
Stack archaeology. Identify when a site was last redesigned by checking versions of detected libraries.
Vendor due diligence. Quickly verify a provider really does run on the platform they claim in their pitch.

What we deliberately do not do

No JavaScript execution. We fetch the raw HTML response and parse what it contains, including inline <script> tags — but we do not render the page. This means client-side-only frameworks (a pure SPA with empty <body>) will leak less information; for those we rely on response headers and the bundle URL paths to fingerprint the stack. Sites that block bot traffic at the edge may return a cleaner page than a real browser would — the result honestly reflects what their server gave us.

Frequently asked questions

How is this different from "view source"?

View source shows the raw HTML; Site Info parses it for you, runs a fingerprint pass across ~1,500 known products, and presents the result as a tidy report. The same information is reachable manually with patience — but you would need to remember which class name belongs to React vs Vue, which header belongs to Cloudflare vs Fastly, and which generator tag means Drupal 9 vs Drupal 10. We do that lookup for you.

Why does the tech list miss something I know is on the site?

Three common reasons. (1) The thing only loads after JavaScript runs — we do not execute JS, so client-only widgets are invisible to us. (2) The site is behind a service worker that rewrites markup before the user sees it. (3) The signature for that product is not in our database; if a known product is consistently missed, please report it. The reverse — false positives — is rare because each signature requires multiple matching markers.

Does the tool follow redirects?

Yes, up to five hops. The full chain is shown in the report — useful for spotting accidental redirect loops, mixed HTTP/HTTPS hops, or canonical-tag mismatches with the final URL. If your site does more than five redirects we stop and report it as a chain problem (six or more is almost always a config bug).

Can I use this on private/staging sites?

Only if they are publicly reachable. The fetch runs from our Frankfurt server, so anything behind a VPN, IP allowlist, or basic-auth wall will fail. RFC 1918 private ranges and link-local addresses are refused at the SSRF guard. For internal staging, run a local tech-detection tool (e.g. the Wappalyzer browser extension) from inside your network.