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
83/100
SECURITY SCORE
Certificate Information
Subject
CN=rortizauto.com
Issuer
C=US, O=DigiCert, Inc., CN=Encryption Everywhere G3 TLS ECC P384 SHA384 2023 CA1
Valid From
April 04, 2025
Valid Until
April 03, 2026
86 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
E0:B3:CE:00:AA:8D:CF:03:27:85:8F:DE:21:4E:59:8C:B8:69:16:B7:95:64:B7:1E:82:72:C0:65:6B:75:32:CE
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
Weak
max-age=0
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Excellent
deny
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