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:
Invalid Certificate - the server's certificate is malformed or invalid
Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=vpn.wakefern.com
Issuer
CN=vpn.wakefern.com
Valid From
March 27, 2024
Valid Until
March 25, 2034
2982 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA512-RSA
SHA-256 Fingerprint
70:F2:F9:50:1E:A4:29:AB:BE:FF:88:89:FF:8A:F8:2E:F4:B7:10:CA:C9:92:D2:D1:67:F5:BF:87:1E:47:08:06
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Good
default-src; script-src; style-src; +10 more
default-src 'self' ; script-src 'self' ; style-src 'self' ; block-all-mixed-content; base-uri 'self'; object-src 'none'; worker-src 'self' ; connect-src 'self' ; child-src 'self' ; font-src 'self' data: ; form-action 'self' ; media-src 'self' ; img-src data: 'self' 'unsafe-inline' ;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
camera=(), geolocation=(), microphone=()
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Strengthen CSP by removing 'unsafe-eval'
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