Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=neat.no
Issuer
C=US, O=DigiCert, Inc., CN=Encryption Everywhere G3 TLS ECC P384 SHA384 2023 CA1
Valid From
September 26, 2025
Valid Until
September 25, 2026
307 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
AB:7F:9E:56:CE:BE:EF:16:93:90:58:6F:CC:02:6B:CD:E9:3B:57:35:EB:15:C0:FB:9B:3D:97:8B:C3:46:3A:ED
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=31536000
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
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports