Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=namely.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 03, 2025
Valid Until
February 01, 2026
83 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BA:B3:5F:14:9B:02:E5:AF:C5:BB:65:2A:65:43:E3:D8:AA:1C:D8:08:7B:80:D3:2E:A7:1C:07:57:FF:24:D7:56
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
Weak
base-uri
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
ch-viewport-width=(self "https://mlnq5qmsdxfa.i.optimole.com"), ch-ect=(self "https://mlnq5qmsdxfa.i.optimole.com")
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