Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=*.castingfrontier.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
March 09, 2025
Valid Until
April 06, 2026
93 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8E:77:7B:09:1F:51:A1:62:DC:7E:6A:25:4B:30:8F:CE:BD:57:34:13:8E:90:F6:26:19:00:E3:B3:ED:5B:DD:92
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
Missing
Not configured
Content-Security-Policy
Weak
font-src; img-src; object-src; +3 more
font-src 'self' https: http: data: *.s3.amazonaws.com; img-src 'self' https: http: data: *.s3.amazonaws.com; object-src 'none'; frame-ancestors 'self'; block-all-mixed-content; upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
- • 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