Cached · just now
93/100 SECURITY SCORE

Certificate Information

Subject
CN=engagement.coremedia.cloud
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
February 18, 2026
Valid Until
March 19, 2027 316 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BF:F0:DB:0D:BC:07:DB:44:05:B2:CF:68:E0:58:5D:A4:1B:60:B1:A9:39:76:8D:1A:23:67:A2:B2:0F:7A:C9:63
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
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; script-src; style-src; +3 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(self "https://byside.com" "https://*.byside.com" "https://coremedia.cloud" "https://*.coremedia.cloud"), microphone=(self "https://byside.com" "https://*.byside.com" "https://coremedia.cloud" "https://*.coremedia.cloud"), camera=(self "https://byside.com" "https://*.byside.com" "https://coremedia.cloud" "https://*.coremedia.cloud"); +2 more
Recommendations
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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