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:
Hostname Mismatch - certificate is issued for *.zoholandingpage.zohohost.com, *.zohosites.com, *.zylker.com, *.zylkertravels.com, zhs.zoholandingpage.com, zohosites.com, zohouniv.com, zylker.com, zylkertravels.com, not for www.avion-solutions.com
Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=*.aviontech.me
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 02, 2026
Valid Until
April 02, 2026
50 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
4A:16:2F:76:FC:F8:B2:6E:50:FA:55:B9:D2:4D:22:B6:B0:50:0E:3F:FA:FE:C5:6A:FF:90:5F:68:1B:A6:5D:7A
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
Excellent
max-age=64072000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • 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