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

Certificate Information

Subject
CN=*.cloudemail.be
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
October 05, 2025
Valid Until
January 03, 2026 43 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0F:E7:8F:73:BF:25:32:2E:C0:53:6D:C1:C6:53:95:CC:11:67:4B:4D:4F:95:13:1E:D0:D9:54:3B:A7:4D:BA:BE
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
Present
max-age=16000000; includeSubDomains; preload;
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Significantly strengthen CSP directives
  • • 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