SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for arizent.arizent.production.k2.m1.brightspot.cloud, *.arizent.arizent.production.k2.m1.brightspot.cloud, not for information-management.com
Open
Cached
·
just now
76/100
SECURITY SCORE
Certificate Information
Subject
CN=origin.arizent.arizent.production.k2.m1.brightspot.cloud
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
May 22, 2025
Valid Until
June 20, 2026
156 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
73:59:7C:25:1D:A1:B2:3F:D0:77:A4:B1:1A:26:1E:B9:FE:59:0A:3D:13:1E:2F:12:C3:88:09:DE:20:34:7B:C6
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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
Subject Alternative Names
9 domains
arizent.arizent.production.k2.m1.brightspot.cloud
*.arizent.arizent.production.k2.m1.brightspot.cloud
cms.arizent.arizent.production.k2.m1.brightspot.cloud
*.cms.arizent.arizent.production.k2.m1.brightspot.cloud
origin.arizent.arizent.production.k2.m1.brightspot.cloud
*.origin.arizent.arizent.production.k2.m1.brightspot.cloud
static.arizent.arizent.production.k2.m1.brightspot.cloud
verify.cms.arizent.arizent.production.k2.m1.brightspot.cloud
verify.origin.arizent.arizent.production.k2.m1.brightspot.cloud