Open
Cached
·
4h ago
89/100
SECURITY SCORE
Detected Technologies
Cloudflare
Active incidents
AppNexus (Xandr)
Authorize.net
Amazon S3
Bing
Ceros
Cloudflare CDNJS
Contentsquare
Demandbase
Oracle Eloqua
GitHub
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Static File Front End
Google Tag Manager
Liveramp
Microsoft Clarity
Optimizely
YouTube
Cloudflare CA
Google Cloud
Certificate Information
Subject
CN=developer.authorize.net
Issuer
C=US, O=CLOUDFLARE, INC., CN=Cloudflare TLS Issuing ECC CA 1
Valid From
April 03, 2026
Valid Until
October 19, 2026
156 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
14:8A:CE:0A:3C:8D:3E:13:A7:96:2B:DE:EE:F0:A4:64:D8:48:FF:8A:30:66:64:79:30:03:E5:F3:7E:E9:2E:EB
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; includeSubdomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Present
nosniff, 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
- • 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