DNS Gurus
Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=analytx.incentx.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
November 07, 2025
Valid Until
February 05, 2026 40 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
95:21:2B:D0:8C:1F:63:C6:F0:EF:E9:19:0A:9E:E7:B5:84:FD:79:88:CF:5E:3D:61:6F:A7:C6:A0:E1:C2:CB:03
Alternative Names
54 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=64072000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer, strict-origin-when-cross-origin
Permissions-Policy
Present
clipboard-read=(self), geolocation=(self), camera=(self), microphone=(self), clipboard-write=(self), payment=(), usb=(), display-capture=(self)
Recommendations
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking

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