Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=*.keyringapp.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
December 03, 2025
Valid Until
January 01, 2027
355 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A2:C1:77:E4:6E:11:56:9A:78:7C:95:E9:57:DD:BC:C9:42:55:2E:AF:6B:02:18:63:38:F6:75:87:DD:56:E9:5D
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Strong
default-src; font-src; img-src; +3 more
default-src 'self' https:; font-src 'self' https: data:; img-src 'self' https: data:; object-src 'none'; style-src 'self' https:; script-src 'self' https:
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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