Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=assets.zettle.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 20, 2026
Valid Until
July 19, 2026
75 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
AD:57:0B:5F:72:42:C7:77:38:74:CD:6E:D2:D9:81:40:99:A3:19:7C:B7:55:BA:AC:12:AA:A0:3F:EB:B5:14: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
Excellent
max-age=63072000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
ch-ua-platform-version=(self "https://c.paypal.com"), ch-ua-arch=(self "https://c.paypal.com"), ch-ua-wow64=(self "https://c.paypal.com"); +4 more
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
awstrust.com
digicert.com
letsencrypt.org
; validationmethods=http-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/23216805
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance