Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=*.scim.io
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
June 18, 2025
Valid Until
July 16, 2026
202 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BC:09:E5:5A:9D:2F:31:ED:05:E0:7E:C4:06:3D:31:8D:F3:7D:D8:F4:27:13:BA:FB:B3:5D:66:DB:36:6A:AB:5A
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=63072000; includeSubdomains; preload
Content-Security-Policy
Basic
default-src; frame-ancestors; img-src; +2 more
default-src * 'unsafe-inline' 'unsafe-eval' data:; frame-ancestors 'self' *.ips.cloud *.au.ips.cloud *.app.netsuite.com *.whatsglide.com *.glideworkflow.com *.glideworkpm.com *.lightning.force.com *.visualforce.com *.force.com; img-src * data: blob:; worker-src * data: blob:; frame-src * data: blob:
X-Frame-Options
Present
ALLOW-FROM=*.force.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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