Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=paystack.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
July 06, 2026
Valid Until
October 04, 2026
48 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
EC:F9:B5:48:75:A9:EB:81:1E:81:CB:39:06:8B:3B:63:05:39:EB:CD:A7:B5:D7:9B:DA:D6:E3:59:1E:B5:A0:7B
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
Present
same-origin
Permissions-Policy
Present
accelerometer=(), camera=(), clipboard-read=(); +13 more
Recommendations
- • 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