Open
Cached
·
just now
79/100
SECURITY SCORE
Detected Technologies
Gravatar
Amazon Advertising
AMP
Auth0
AWS Certificate Manager
Amazon S3
BootstrapCDN
Cloudflare CDNJS
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Search
Google Tag Manager
jQuery
jQuery Migrate
jsDelivr
List.js
New Relic
PubMatic
Stripe
TripleLift
Twitter
WordPress
Google Cloud Storage
Underscore.js
Certificate Information
Subject
CN=*.wordnik.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
April 08, 2026
Valid Until
October 22, 2026
168 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C2:A7:96:66:98:69:D6:65:13:A6:84:6A:6A:E8:AA:F1:BA:E0:71:E2:A7:6F:D0:B7:17:B4:CD:F5:6E:8E:83:69
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
- • 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
Present
max-age=15552000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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