Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=*.fieldagentstaging2.sentera.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
October 03, 2025
Valid Until
November 01, 2026
344 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8B:B5:7A:31:60:B6:CE:4F:06:CC:5F:68:F2:9E:3B:09:24:E6:B2:53:07:6C:25:67:70:CB:C9:FE:8D:FB:13:26
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
script-src; object-src; style-src; +1 more
script-src 'self' 'unsafe-eval' 'unsafe-inline' api.mapbox.com cdnjs.cloudflare.com blob:; object-src 'self'; style-src 'self' 'unsafe-inline' fonts.googleapis.com; frame-ancestors 'self'
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
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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