Domain A · External perimeter
Automated coverage
Behind each external-perimeter check group (A01–A12) runs a set of automated probes: DNS and mail records, TLS and cipher suites, security headers, exposed files and open ports, and software-version matching. This page shows what the automated layer actually tests. Application, code, infrastructure, data and AI/Agent domains, and levels V2–V4, add expert scenarios — see the methodology.
Automated probes per perimeter group
A group passes only when every applicable probe passes or is formally not applicable. The figures below are the size of the automated signature set — not a score, and not a per-product test count.
TLS & certificate
Protocol versions, cipher suites, chain, expiry, key strength.
≈170 probes, incl. 122 cipher-suite tests · automated
HTTPS & HSTS
HTTP→HTTPS redirect, HSTS lifetime, subdomains, preload.
7 probes · automated
DNS & zone hygiene
DNSSEC, CAA, nameservers, AXFR, dangling records.
30 probes · automated
Email authentication
SPF, DKIM, DMARC, MTA-STS, TLS-RPT.
40 probes · automated
Security headers
CSP, frame protection, nosniff, referrer, permissions.
45 probes · automated
Exposed services & ports
Listening services and management ports on the perimeter.
≈1,000 port probes · automated
Known-vulnerable versions
Detected components matched to CVE/NVD and CISA KEV.
104 version signatures · automated
Admin & default creds
Reachable admin panels; default or vendor credentials.
34 probes · automated + review
Information disclosure
Banners, listings, VCS folders, env files, backups, traces.
≈5,100 path signatures, most informational · automated
Cookie attributes
Secure, HttpOnly, SameSite, scope and lifetime.
20 probes · automated
Redirects & mixed content
Open redirects, downgrade paths, mixed content.
17 probes · automated
Disclosure channel
Published, monitored way to report a vulnerability.
1 probe · automated
Signature sources
The automated layer is built from recognised, openly published data sets, refreshed by edition. Each probe maps to exactly one perimeter check group.
Signature-set size is not a test count. Most A09 path signatures map the surface and are informational; only a minority indicate real exposure.
What the automation is — and is not
Automation screens the external perimeter and feeds the pass/fail result of each perimeter group, with evidence stored for every check. It does not replace the expert scenarios required for the application, code, infrastructure, data and AI/Agent domains, or for levels V2–V4.
The Trust Page for a certificate lists the components actually assessed, the methods used, the results and the limitations — never vulnerability details.
Related: V-Standard methodology · Levels & pricing · Public registry