Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=paybis.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 09, 2025
Valid Until
March 09, 2026
55 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
D1:F2:80:F9:BF:60:AD:8B:83:3B:DC:DA:FA:0D:58:41:B4:5B:7C:2B:50:AE:49:F5:F9:C3:C0:CD:74:48:5A:7A
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=15552000
Content-Security-Policy
Strong
default-src; script-src; frame-src; +6 more
default-src 'none'; script-src 'self' static.cloudflareinsights.com; frame-src 'self'; connect-src 'self' https://cardentry-api.paybis.com cloudflareinsights.com; img-src 'self'; style-src 'self'; base-uri 'self'; form-action 'self'; font-src 'self'
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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