DNS Gurus

SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Hostname Mismatch - certificate is issued for preprod.pearsonactivelearn.com, dev.pearsonactivelearn.com, devsso.pearsonactivelearn.com, perf.pearsonactivelearn.com, preview.dev.pearsonactivelearn.com, preview.preprod.pearsonactivelearn.com, preview.qa.pearsonactivelearn.com, qa.pearsonactivelearn.com, qasso.pearsonactivelearn.com, not for preview.dev.pearsonactivelearn.pearson-intl.com

Cached · just now
76/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Sectigo logo Sectigo

Certificate Information

Subject
C=GB, ST=London, O=Pearson PLC, CN=preprod.pearsonactivelearn.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R36
Valid From
December 02, 2025
Valid Until
December 02, 2026 219 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
55:9C:72:93:47:5C:7A:89:6A:9F:DC:65:45:3F:D3:B9:44:73:D3:51:77:42:99:F3:93:88:55:1D:5E:42:3D:45
Alternative Names
18 domains

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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