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

Certificate Information

Subject
CN=haproxy0.frontend1.inwx.de
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
December 02, 2025
Valid Until
March 02, 2026 89 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B7:CA:90:94:14:02:C3:CA:3E:54:E5:9A:89:AC:C0:36:F2:FF:BA:8A:17:03:74:E0:97:89:46:B0:8D:2F:B2:88
Alternative Names
15 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
Present
max-age=15768000; includeSubDomains; always;
Content-Security-Policy
Basic
default-src; connect-src; worker-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • 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