Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
CN=prod.wisembly.mediactive-network.net
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 16, 2025
Valid Until
February 14, 2026 47 days
Public Key
RSA 3072 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
14:D5:7E:53:31:1A:E1:63:5E:B2:43:69:FF:19:F0:C8:E2:2C:25:99:D6:D0:5A:65:8B:E7:C6:C0:E0:87:6C:89
Alternative Names

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=2592000; includeSubDomains; preload
Content-Security-Policy
Weak
connect-src; media-src
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(), camera=*, cross-origin-isolated=(), display-capture=(), encrypted-media=(), fullscreen=*, geolocation=(), gyroscope=(), keyboard-map=(), magnetometer=(), microphone=*, midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=*, usb=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(), clipboard-write=(), gamepad=()
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives

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