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 blockdaemon.app, cardano.blockdaemon.com, solana.blockdaemon.com, stellar-0.blockdaemon.com, stellar-1.blockdaemon.com, stellar-2.blockdaemon.com, stellar.blockdaemon.com, toml-server.man.bdi.sh, www.blockdaemon.app, not for blog.blockdaemon.com

Cached · just now
80/100 SECURITY SCORE

Certificate Information

Subject
CN=toml-server.man.bdi.sh
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 13, 2026
Valid Until
April 13, 2026 87 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
15:F2:7D:1D:7B:31:B6:6E:38:B7:72:26:08:38:FA:30:86:76:30:B8:B2:EE:36:BC:12:35:3A:E9:77:B4:04:CD
Alternative Names
9 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
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Significantly strengthen CSP directives
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • 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