CMS detection
The system that built the pages, recognised from the markup and the headers. Likely means it was matched on a path rather than on something the site declares outright.
A content management system or site builder — WordPress, Joomla, Drupal, Shopify, Wix, Tilda, Bitrix and dozens of others — is what produces the site's HTML. Knowing which one a site runs tells you where its pages come from, which plugins and updates to watch, and which known weaknesses apply.
How SiteScan recognises it
Only the entry page is read; no extra requests are made.
- Green — the site declares the platform itself: a
<meta name="generator">tag or a header only that system sends (for exampleX-Pingbackpointing atxmlrpc.phpon WordPress). The version is shown when the declaration includes one. - Amber, "likely" — the platform was matched on a fingerprint in the markup, such as
/wp-content/paths. That is strong evidence but not a statement, so the report says "likely". Amber here is not a fault. - Grey, "not recognised" — a hand-built site, a framework, or a platform that leaves no trace.
Good practice
A generator tag with an exact version, such as WordPress 6.5.2, tells an attacker how far behind you are. Remove it — most platforms have a setting or a one-line filter for it — and, more importantly, keep the core, themes and plugins updated. The rest of the stack is listed under detected technologies.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Technology”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data