Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Google Trust
Google AdSense
Canny
Zscaler
Google Tag Manager
Forethought
WP Engine
HubSpot Forms
Pendo
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Segment
New Relic
Basis Technologies
Datadog
Google Cloud Storage
Google Static File Front End
Google Fonts
Clickagy
Wistia
Twitter
LinkedIn
Zendesk
Entri
ZoomInfo
Stripe
Google Search
Qualified
Facebook
Mouseflow
Rollbar
HubSpot
YouTube
Google Cloud
Certificate Information
Subject
CN=my.wpengine.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 05, 2026
Valid Until
July 04, 2026
59 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
B9:25:B5:6A:B9:0C:E5:27:B8:53:D7:51:0D:1D:17:77:F8:86:16:6D:F3:47:C3:39:A4:DB:08:D2:87:0D:5B:99
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
Good
max-age=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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