Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=www.fieldclock-static.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
June 11, 2025
Valid Until
July 09, 2026
157 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
9D:8A:0F:67:62:2F:B9:FC:E6:56:D7:8A:35:6D:E7:CA:5B:AC:CD:2F:E4:36:F9:2C:C7:3D:E6:9A:7E:2E:5D:52
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
Content-Security-Policy
Good
default-src; img-src; script-src; +3 more
default-src 'self' *.fieldclock.com www.fieldclock-static.com https://static.zdassets.com https://ekr.zdassets.com https://fieldclockapp.zendesk.com https://*.zopim.com wss://fieldclockapp.zendesk.com wss://*.zopim.com; img-src 'self' *.fieldclock.com www.fieldclock-static.com img.youtube.com data: https://v2assets.zopim.io https://static.zdassets.com; script-src 'self' *.fieldclock.com www.fieldclock-static.com www.google-analytics.com www.googletagmanager.com use.fontawesome.com https://static.zdassets.com https://ekr.zdassets.com https://fieldclockapp.zendesk.com https://*.zopim.com wss://fieldclockapp.zendesk.com wss://*.zopim.com; style-src 'self' *.fieldclock.com www.fieldclock-static.com fonts.googleapis.com use.fontawesome.com 'unsafe-inline'; font-src 'self' *.fieldclock.com www.fieldclock-static.com fonts.gstatic.com use.fontawesome.com; object-src 'self' *.fieldclock.com www.fieldclock-static.com use.fontawesome.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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