Cached · just now
83/100 SECURITY SCORE

Certificate Information

Subject
CN=digdir.no
Issuer
C=NO, O=Buypass AS-983163327, CN=Buypass Class 2 CA 2
Valid From
September 26, 2025
Valid Until
September 26, 2026 237 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1E:53:D5:FB:BA:15:6F:80:88:66:B7:BE:36:A2:D0:35:5D:5F:CC:49:58:70:91:A6:96:F3:27:85:5A:26:10:40
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
Present
max-age=63072000;
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Add Content-Security-Policy header to prevent XSS attacks
  • 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
Not Authorized (Potential misconfiguration)
Incident Reporting
CAA Issues
  • CRITICAL: Current certificate issuer 'C=NO, O=Buypass AS-983163327, CN=Buypass Class 2 CA 2' is NOT authorized by CAA records. Authorized CAs: digicert.com, commfides.com, buypass.no, sectigo.com, letsencrypt.org
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • You have authorized 5 CAs - consider limiting to only the CAs you actively use
  • Consider adding 'issuewild' records to control wildcard certificate issuance