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 buy.rasaroyal.com
Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=*.shop.rasaroyal.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 25, 2025
Valid Until
March 25, 2026
74 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F0:1B:C4:31:3B:B1:E4:70:EE:F7:6F:98:AB:A8:75:3E:CC:4A:74:BE:2A:A7:7C:84:78:46:00:4E:D9:48:A5:FA
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
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Content-Type-Options: nosniff
- • 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