DNS Gurus
Cached · just now
90/100 SECURITY SCORE

Certificate Information

Subject
CN=*.datasite.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
December 30, 2025
Valid Until
March 30, 2026 54 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
09:7F:57:64:DC:06:CF:53:5C:78:92:83:8D:00:7F:1A:92:6C:97:0B:96:5A:15:AB:B8:E0:79:94:80:7C:F9:F0
Alternative Names
6 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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
midi=(), magnetometer=(), gyroscope=(), payment=(), microphone=()
Recommendations
  • • Add Content-Security-Policy header to prevent XSS attacks

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