Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=*.mixmax.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
December 24, 2025
Valid Until
January 21, 2027
358 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
4C:80:81:37:6A:8F:09:94:40:D4:90:11:06:AF:B9:A4:5F:1E:8A:6A:48:B7:31:2B:97:7C:2A:0E:F4:EE:32:54
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors; frame-src; report-uri
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
geolocation=(self "https://*.mixmax.com" "https://mail.google.com" "https://*.force.com" "https://*.salesforce.com" "https://outlook.office.com" "https://outlook.live.com" "https://outlook.office365.com"), microphone=(self "https://*.mixmax.com" "https://mail.google.com" "https://*.force.com" "https://*.salesforce.com" "https://outlook.office.com" "https://outlook.live.com" "https://outlook.office365.com"), payment=(self)
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • 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