§Trust Page
ActiveDemo record
V1Surface Verified
Example Site
Owner: Example Technologies · www.example.com
Corporate website and documentation portal.
5 / 5
5 of 5 checks passed
Critical 0High 0
A certificate is not a promise of absolute security. It confirms the results of the checks only within the published scope, on the stated date and under the stated version of the methodology.
Not covered by this certificate
- Web application logic and authenticated areas
- Source code, dependencies and infrastructure
Scope of the certificate
- Components in scope
- Domains and DNS
- Domains in scope
- www.example.com, example.com
- Environment
- Production
- Methodology
- V-Standard 2026.3
- Level
- V1 · Surface Verified
Verified checks
Each row names the check, its method, the date and a public evidence summary. Technical details are held privately by CyberSecurityV.
A · External perimeter
A01 TLS configuration and certificate validityPublic endpoints negotiate only modern protocol versions with a valid, correctly chained certificate. Automated check Passed
Public evidence summaryTLS 1.2 and 1.3 only; valid certificate chain, 84 days to expiry.
CheckSupported protocol versions and cipher suites, certificate chain, expiry, revocation information, key strength and known TLS weaknesses on every public endpoint in scope.
A02 HTTPS enforcement and HSTSAll traffic in scope is forced to HTTPS and protected by HSTS. Automated check Passed
Public evidence summaryHTTP redirects to HTTPS; HSTS max-age 1 year with subdomains.
CheckPlain-HTTP requests are redirected to HTTPS, HSTS is present with an adequate lifetime, and no content in scope is served over an unencrypted channel.
A03 DNS configuration and zone hygieneNo dangling records or takeover conditions were found in the domains in scope. Automated check Passed
Public evidence summaryAuthoritative servers consistent; no dangling records among 9 records in scope.
CheckAuthoritative servers, DNSSEC where applicable, dangling records that allow sub-domain takeover, zone transfer exposure and consistency between public and expected records.
A05 HTTP security headersSecurity headers are present and configured without unsafe exceptions on the pages in scope. Automated check Passed
Public evidence summaryCSP, frame protection, nosniff, referrer and permissions policies present without unsafe exceptions.
CheckContent-Security-Policy, frame protection, content-type sniffing, referrer policy, permissions policy and cache directives on sensitive responses.
A06 Exposed services and open portsOnly the intended services are reachable from the internet. Automated check Passed
Public evidence summaryOnly 80/443 reachable; no management ports or unexpected services on the two hosts in scope.
CheckInventory of listening services on the public perimeter, unexpected management ports, databases or message brokers reachable from the internet.
Verification history
- Application submitted
- Certificate issued
Verify this record
The registry record behind this page is signed with the CyberSecurityV registry key. Your browser can verify the signature and the fingerprint without contacting anyone but the registry.
Record fingerprint (SHA-256): 7bcd8546d13836b7fa42f189da5498467a647421d518863c351a634d073c7929
Registry signature (Ed25519): NVHcvdOrTB+mAqnvLQJ4aUxA0XNuFkXStvbx+A9eHDLKTNrCgnu039nQg0IQjyfH5qPfdpwC+S7VeZQQ4lAEAA==