SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Unknown Certificate Authority - the server's certificate is not trusted
Open
Cached
·
just now
74/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=California, L=Santa Barbara, O=SSL Server, OU=For Testing Purposes Only, CN=localhost, UNKNOWN=root@localhost
Issuer
C=US, ST=California, L=Santa Barbara, O=SSL Server, OU=For Testing Purposes Only, CN=localhost CA, UNKNOWN=root@localhost
Valid From
December 21, 2020
Valid Until
December 21, 2022
Expired
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
05:81:25:BC:E6:DE:21:66:26:2B:47:B0:E3:37:6A:BF:71:7A:34:0E:BF:E3:3E:30:56:C8:0A:73:3C:97:9C:10
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=15552000
Content-Security-Policy
Weak
object-src; form-action
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • 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