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 cpanel.marksdiamonds.com, cpcalendars.marksdiamonds.com, cpcontacts.marksdiamonds.com, mail.marksdiamonds.com, marksdiamonds.com, webdisk.marksdiamonds.com, webmail.marksdiamonds.com, whm.marksdiamonds.com, www.marksdiamonds.com, not for www.node220.myfcloud.com
Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=mail.marksdiamonds.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 27, 2026
Valid Until
April 27, 2026
88 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3F:57:D7:7E:E9:AC:BB:FE:F1:EA:4F:D6:90:17:CD:18:03:09:07:3E:69:FD:7B:85:11:0A:FD:09:E1:8D:C4:C0
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
upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
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
- • Significantly strengthen CSP directives
- • 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