Open
Cached
·
just now
81/100
SECURITY SCORE
Certificate Information
Subject
C=BE, ST=Vlaams-Brabant, L=Leuven, O=GlobalSign nv-sa, CN=globalsign.net
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 OV ACME CA 2025 Q2
Valid From
August 30, 2025
Valid Until
August 30, 2026
297 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
4B:F9:DC:7B:4F:DB:D6:6D:3C:6B:95:87:B4:34:68:8B:C4:AD:6D:A5:83:06:1A:A0:D8:F5:73:34:33:8C:07:EE
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance