Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=drivepayments.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 05, 2026
Valid Until
April 05, 2026
39 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
4A:49:CA:1E:3E:A5:BD:09:B9:E9:B9:DD:82:F3:DB:E2:FF:E6:11:40:2A:B8:DD:E6:D3:B8:AB:96:C3:08:BC:F5
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=63072000;includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), bluetooth=(); +13 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
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