Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
PayPal
AWS API Gateway
AWS CloudFront
YouTube
Google AdSense
Google Tag Manager
Azure Blob Storage
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Loggly
Active incidents
Google Static File Front End
LaunchDarkly
Google API JS Client
Google Fonts
Hotjar
LinkedIn
LiveChat
unpkg
Google Search
Facebook
Amazon S3
OneTrust
Salesforce Sites
Storyblok
AWS
Active incidents
jQuery
Salesforce Pardot
Taboola
AWS Certificate Manager
Vimeo
Sentry
Google Cloud
Certificate Information
Subject
CN=br.izettle.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
September 06, 2025
Valid Until
October 04, 2026
146 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
63:CC:A1:78:47:AD:F0:C0:10:38:17:17:87:36:AF:53:11:D3:0C:BC:F6:46:15:15:87:87:E0:5A:60:54:2F:78
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=31536000; includeSubDomains; preload
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
- • 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