DNS Gurus
Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=jiraanalytics.manageengine.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
November 21, 2025
Valid Until
February 19, 2026 48 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
69:B6:5B:3C:46:E1:91:C6:AA:17:C0:9A:74:7B:29:A1:47:AE:5F:9F:BD:BD:68:1C:34:DA:64:32:2C:C4:EC:7D
Alternative Names
5 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