Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
Akamai
Active incidents
Akamai mPulse
Algolia
AppNexus (Xandr)
Microsoft Advertising
Demandbase
Facebook
Google AdSense
Google Analytics
Google DoubleClick
Google Fonts
Hotjar
jsDelivr
LaunchDarkly
LinkedIn
New Relic
OneTrust
Quora
Reddit
Salesforce Pardot
Salesforce Sites
Sectigo
Snapchat
Spotify
TikTok Analytics
The Trade Desk
Twitter
Visual Website Optimizer
YouTube
Certificate Information
Subject
C=GB, ST=London, O=Pearson PLC, CN=*.pearson.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R36
Valid From
May 23, 2025
Valid Until
May 23, 2026
41 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
62:73:2F:43:64:16:76:0D:50:7F:22:01:FD:3F:5A:09:DA:B6:44:D3:51:25:4B:78:24:D0:42:82:D9:40:5F:EE
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 ; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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