Open
Cached
·
6h ago
89/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=jmi.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 26, 2026
Valid Until
July 25, 2026
72 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5B:48:9D:3A:76:A3:5F:5D:89:30:E1:B4:BE:AC:71:F0:8D:CF:F8:16:E3:8F:7A:9A:B0:B4:41:A3:77:A1:3B:1B
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, max-age=31536000;
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Present
nosniff, nosniff
Referrer-Policy
Present
strict-origin-when-cross-origin, no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(), autoplay=(), camera=(); +19 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
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