Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=*.digitevent.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
November 22, 2025
Valid Until
December 20, 2026
331 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1D:85:EB:FB:D4:A3:2F:46:F8:E5:6C:77:53:60:61:14:CC:2D:23:AC:DC:0C:CE:2E:A7:1D:17:32:3B:BE:A3:FC
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=15552000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; style-src; connect-src; +6 more
default-src 'self'; style-src 'self' 'unsafe-inline' https://unpkg.com/[email protected]/swagger-ui.css; connect-src 'self' https://unpkg.com/[email protected]/swagger-ui.css.map; script-src 'self' 'unsafe-inline' https://unpkg.com/[email protected]/swagger-ui-bundle.js; img-src 'self' data:; object-src 'self'; base-uri 'none'; report-uri /security/csp/violation; frame-src 'self'
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Consider adding Permissions-Policy to control browser features
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