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 *.nerds.sh, nerds.nerdscomputing.com, nerds.sh, www.nerds.nerdscomputing.com, not for ftp.nerdscomputing.com
Open
Cached
·
10m ago
89/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=www.nerds.nerdscomputing.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 29, 2026
Valid Until
July 28, 2026
76 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
02:23:89:FB:45:E5:62:2D:8D:07:DC:12:D5:F7:36:99:8A:2D:A5:5C:06:09:25:2C:D9:49:2E:C2:14:CE:B9:BB
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=31536000; includeSubDomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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
Subject Alternative Names
4 domains
nerds.nerdscomputing.com
www.nerds.nerdscomputing.com
nerds.sh
*.nerds.sh
Other domains in certificate