DNS Gurus
Open Cached · just now
85/100 SECURITY SCORE

Certificate Information

Subject
CN=capido.be
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 17, 2025
Valid Until
February 15, 2026 71 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F7:FE:E8:D9:3F:B9:A0:67:30:99:76:A0:85:32:8B:4B:E9:64:70:9F:83:ED:C4:A6:53:F7:F2:2A:CB:EB:4A:D6
Alternative Names
10 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
Good
SAMEORIGIN
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