Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=dev.bytepad.com
Issuer
C=US, O=DigiCert, Inc., CN=GeoTrust Global TLS RSA4096 SHA256 2022 CA1
Valid From
January 03, 2026
Valid Until
April 14, 2026
92 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A0:F3:5D:AF:25:80:C8:C6:5F:5E:57:78:3C:4D:99:A2:5C:39:85:5E:C5:49:CD:BF:E8:69:49:42:BC:22:F7:0D
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=15552000; includeSubDomains; preload
Content-Security-Policy
Good
frame-ancestors; script-src; default-src; +9 more
frame-ancestors 'self' preview.athenahealth.com *.epic.com *.epichosted.com proud-moss-0ec0d0c0f.5.azurestaticapps.net iframetester.com dev.bytepad.com localhost:3030 api.preview.athenahealth.com pmsai-dev.bytepad.com ;script-src 'self' blob: https: preview.athenahealth.com *.epic.com *.epichosted.com proud-moss-0ec0d0c0f.5.azurestaticapps.net iframetester.com dev.bytepad.com localhost:3030 api.preview.athenahealth.com pmsai-dev.bytepad.com ;default-src 'self' data: https: blob: preview.athenahealth.com *.epic.com *.epichosted.com proud-moss-0ec0d0c0f.5.azurestaticapps.net iframetester.com dev.bytepad.com localhost:3030 api.preview.athenahealth.com pmsai-dev.bytepad.com ;connect-src 'self' https: data: blob: wss://pmsai-dev.bytepad.com wss://dev.bytepad.com wss://localhost:3030 data: blob: ;img-src 'self' data: blob: https:;object-src 'self';upgrade-insecure-requests;base-uri 'self';font-src 'self' https: data:;form-action 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(), microphone=(), camera=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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