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 pc3.atmailcloud.com, *.pc3.atmailcloud.com, us-east.atmailcloud.com, *.us-east.atmailcloud.com, not for webmail.tecinfo.com
Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=pc3.atmailcloud.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
May 05, 2025
Valid Until
June 03, 2026
131 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0B:E7:C3:84:A1:58:D0:77:BB:30:85:F6:7E:0B:3E:58:04:00:C0:3A:81:6E:25:36:F9:79:B1:88:58:4A:99:7D
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=63072000; includeSubDomains
Content-Security-Policy
Basic
default-src; connect-src; frame-src; +3 more
default-src 'self' jmap-api.pc3.atmailcloud.com; connect-src 'self' jmap-api.pc3.atmailcloud.com admin.pc3.atmailcloud.com graph.microsoft.com www.dropbox.com apis.google.com www.google-analytics.com js.live.net api.onedrive.com webmail2.ftc-i.net legacy-www.mail.fm; frame-src *; script-src 'self' ssl.google-analytics.com www.google-analytics.com graph.microsoft.com www.dropbox.com apis.google.com js.live.net 'unsafe-inline' 'unsafe-eval'; img-src * data: blob: 'unsafe-inline'; style-src * 'unsafe-inline';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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