Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Adobe Target
Adobe Audience Manager
Adobe Experience Cloud
Advertising.com
AppNexus (Xandr)
Bing
Microsoft Advertising
Criteo
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Hosted Libraries
Google Search
Google Tag Manager
jQuery
OpenX
Outbrain
PubMatic
Rubicon Project
Sectigo
Tapad
Tealium
The Trade Desk
Yahoo
Certificate Information
Subject
C=TW, ST=Taipei, O=HSBC Bank (Taiwan) Limited, CN=loan.apply.hsbc.com.tw
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R36
Valid From
June 23, 2026
Valid Until
January 07, 2027
90 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C3:38:66:AD:33:E1:2F:1A:08:56:67:36:18:26:4D:63:83:04:6B:44:64:E8:6B:C6:7B:E5:E0:09:30:5F:47:74
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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