DNS Gurus

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 unstack.com, *.unstack.website, *.unstack.com, unstackproxy.com, unstack.website, unstacksite.com, *.unstacksite.com, *.unstackproxy.com, not for ec2-3-215-194-38.compute-1.amazonaws.com

Open Cached · just now
84/100 SECURITY SCORE

Certificate Information

Subject
CN=unstack.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
July 13, 2025
Valid Until
August 10, 2026 257 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8D:C8:83:70:85:C3:4A:36:57:4B:E5:9D:38:95:57:57:00:72:24:1A:A0:7D:4F:2A:D9:B6:A0:69:EA:0C:7F:F3
Alternative Names
8 domains

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
Missing
Not configured
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • 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