Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
YouTube
Amazon S3
Contentsquare
Facebook
Framer
Google AdSense
Google Analytics
Google API JS Client
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
LinkedIn
Reddit
Snapchat
Taboola
TikTok Analytics
Twitter
Visual Website Optimizer
ZeroSSL
Google Cloud
Certificate Information
Subject
CN=bunq.com
Issuer
C=AT, O=ZeroSSL, CN=ZeroSSL ECC Domain Secure Site CA
Valid From
March 30, 2026
Valid Until
June 28, 2026
53 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
A2:C5:36:BF:C6:CE:AE:F8:8D:4A:8A:73:85:E3:C2:8E:72:EE:8F:C0:7B:DD:88:02:B4:38:F1:BB:36:4E:9A:4A
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
X-Frame-Options
Missing
Not configured
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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