Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=keychainpay.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
September 24, 2025
Valid Until
October 23, 2026
274 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E0:17:2F:E0:22:3B:BF:23:8F:E0:95:D9:E8:55:BA:8B:1A:D6:4C:1F:44:E0:63:30:19:0F:67:06:48:A4:C0:B8
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
Content-Security-Policy
Basic
default-src; img-src; style-src; +2 more
default-src 'self' *.keychainpay.com *.support.keychainpay.com ajax.googleapis.com fonts.gstatic.com js.stripe.com fonts.googleapis.com test-dahsingbank.mtf.gateway.mastercard.com mtf.gateway.mastercard.com api.bincodes.com; img-src 'self' *.keychainpay.com *.support.keychainpay.com maps.googleapis.com maps.gstatic.com data:; style-src 'self' 'unsafe-inline' fonts.googleapis.com code.jquery.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' *.keychainpay.com *.support.keychainpay.com ajax.googleapis.com maps.googleapis.com api.mailgun.net js.stripe.com code.jquery.com test-dahsingbank.mtf.gateway.mastercard.com dahsingbank.gateway.mastercard.com; frame-ancestors 'self' *.keychainpay.com *.support.keychainpay.com test-dahsingbank.mtf.gateway.mastercard.com dahsingbank.gateway.mastercard.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
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