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 247airservices.com, www.247airservices.com, not for webmail.urated.com
Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=www.247airservices.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 22, 2025
Valid Until
February 20, 2026
35 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F4:2A:99:5F:08:48:3E:9A:FE:D0:D8:D1:08:FD:BE:DC:4C:48:7E:24:38:3E:2D:2D:30:EE:DE:BB:97:F7:BB:CA
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=10886400; preload; includeSubdomains
Content-Security-Policy
Basic
default-src; script-src; style-src
X-Frame-Options
Present
SAMEORIGIN,SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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