Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=app.smartsuite.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
August 02, 2025
Valid Until
August 31, 2026
244 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D0:75:58:B8:26:21:4B:4A:63:94:64:C8:E0:16:22:7E:C6:1F:47:C2:04:BA:D4:F1:99:6E:CA:0E:AC:07:E8:0C
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=31536000; preload
Content-Security-Policy
Basic
base-uri; upgrade-insecure-requests; object-src; +5 more
base-uri 'self'; upgrade-insecure-requests; object-src 'none'; script-src 'nonce-0yU1zbMQeF+VBIqaopzAXg==' 'strict-dynamic'; style-src 'self' *.smartsuite.com *.statuspage.io *.intercomcdn.com messenger-apps.intercom.io webview.canny.io canny.io static.filestackapi.com *.typekit.net *.appcues.com fonts.googleapis.com youtube.com www.youtube.com static.files.smartsuite.com 'unsafe-inline'; font-src 'self' data: *.smartsuite.com *.statuspage.io *.intercomcdn.com messenger-apps.intercom.io webview.canny.io canny.io *.fontawesome.com fonts.gstatic.com use.typekit.net unpkg.com fonts.intercomcdn.com; manifest-src 'self' *.smartsuite.com *.statuspage.io *.intercomcdn.com messenger-apps.intercom.io webview.canny.io canny.io; form-action 'self' *.smartsuite.com *.statuspage.io *.intercomcdn.com messenger-apps.intercom.io webview.canny.io canny.io
X-Frame-Options
Good
SAMEORIGIN
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