Skip to main content

Security report for vue.com

Pearson VUE · Education · United States

Medium risk. 5 critical or high findings in Security headers and GDPR outside view.

Security score

73/100

Risk levelMedium

0–100, higher is better. How it is calculated

Pearson VUE is a leading global provider of certification exam services, delivering high-stakes exams that support professional development and industry standards. The company operates a large network of test centers and offers online proctoring and accommodations to ensure equitable access to testing. Their website is well-branded, professionally designed, and targets test takers, test owners, and training centers with comprehensive resources and navigation. Technically, the site is built on Adobe Experience Manager and hosted on AWS with CloudFront CDN, utilizing modern web technologies including jQuery, Bootstrap, and Font Awesome. Analytics and monitoring are implemented via Google Tag Manager and New Relic. Security posture is solid with key HTTP security headers and HSTS enabled, though SSL configuration requires improvement due to an invalid certificate for the main domain and disabled TLS protocols. Privacy and terms policies are comprehensive and GDPR compliant, but no explicit vulnerability disclosure or incident response contacts are found. Overall, the site demonstrates a mature digital presence with room for security enhancements.

Scanned

This is an earlier scan of vue.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

5 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, LinkedIn, YouTube

      What to do: Document all third-party data sharing in your privacy policy

Need hands-on remediation? Email guard@offseq.com

Keep watching vue.com

This scan found 16 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
95
Security headers
55
Email security
80
DNS health
85
Network security
100
GDPR outside view
25
Average
73

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Pearson VUE holds a strong market position in the education sector as a trusted exam delivery service. Their business model focuses on providing testing infrastructure and services to certification bodies and candidates worldwide. The company benefits from its parent Pearson Education Inc., leveraging a broad partnership ecosystem. Revenue streams likely include exam administration fees and related services. The target audience includes individual test takers, corporate test owners, and training centers. The website content and structure indicate a focus on user support, accessibility, and global reach with multi-language support. The company maintains active social media channels to engage with customers and enhance brand visibility.

Security posture

The website exhibits a good security baseline with strict transport security, frame options, and content type options headers in place. However, the SSL certificate is invalid for the main domain, which poses a risk for user trust and data protection. TLS protocols are disabled, indicating a misconfiguration or incomplete SSL setup. No known vulnerabilities such as Heartbleed or POODLE are detected. The absence of a security.txt file and explicit incident response contacts suggests limited transparency in vulnerability disclosure and incident handling. Privacy policies are comprehensive and GDPR compliant, reflecting a strong data protection culture. Overall, the security posture is moderate with critical improvements needed in SSL configuration and incident response transparency.

Recommendations

  1. Correct the SSL certificate to be valid for vue.com and enable TLS 1.2 or higher protocols.
  2. Implement a security.txt file to provide clear vulnerability disclosure and incident response contacts.
  3. Enable HSTS preload to enhance transport security.
  4. Add explicit incident response contact channels such as security@ or abuse@ emails.
  5. Regularly audit and update security headers and SSL configurations to maintain best practices.
Technical notes

Notes

The website is built on a robust technical infrastructure using Adobe Experience Manager CMS, hosted on AWS with CloudFront CDN for global delivery. It uses modern frontend libraries such as jQuery 3.6.0, Bootstrap 4, and Font Awesome 6.2.1 for UI components and icons. Google Tag Manager and New Relic provide analytics and performance monitoring. The site is optimized for mobile devices and accessibility, with good SEO practices including alternate hreflang tags for multiple languages. Performance is fast with caching and CDN usage. However, the SSL configuration is suboptimal with no TLS protocols enabled and an invalid certificate, which could impact user trust and security compliance. Overall, the technical stack is mature but requires SSL improvements to reduce technical risk.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 62/100 −16Medium26 findingsView report
  2. 78/100Low27 findingsView report
Reviews of this site

Share your experience with vue.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review vue.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.