Skip to main content

Security report for nexis.com

LexisNexis · Other · United States

Medium risk. 4 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

LexisNexis operates as a leading provider of legal, regulatory, and business information services, targeting primarily legal professionals and researchers. The website analyzed is a secure sign-in portal for accessing their research services, reflecting a mature enterprise-level business model with a strong market position. The company provides comprehensive customer support with multiple international phone numbers and maintains clear links to privacy and terms of service policies, demonstrating regulatory awareness and user transparency. Technically, the site employs standard web technologies including jQuery and OneTrust for cookie consent management. While the SSL certificate is valid and issued by a reputable CA, the absence of modern TLS protocols and security headers indicates room for improvement in security hardening. Performance is moderate to slow, and mobile optimization is basic, suggesting potential areas for technical enhancement. From a security perspective, the site shows good foundational practices such as valid SSL and cookie consent but lacks advanced security headers, DNSSEC, and CAA records. No explicit security policies, incident response contacts, or vulnerability disclosure mechanisms were found, which could be addressed to improve security posture and user trust. Overall, the website is professional and trustworthy but would benefit from technical and security upgrades to align with best practices and compliance standards.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 100 · Medium
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

4 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 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

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

Keep watching nexis.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. See sample alerts.

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
75
Security headers
35
Email security
85
DNS health
85
Network security
100
GDPR outside view
58
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

LexisNexis holds a strong position in the legal and business information sector, leveraging subscription-based services to deliver research and analytics. Their target customers are legal professionals and business researchers requiring reliable and comprehensive data. The company benefits from a global presence, as evidenced by multiple international support numbers. The parent company, RELX Group, provides additional corporate strength and resources. The business model focuses on information services with a high degree of regulatory compliance and user data protection, supported by clear privacy and terms documentation. The partnership ecosystem includes RELX and cookie consent providers like OneTrust, indicating a mature operational environment.

Security posture

The current security posture is foundational but not advanced. The site uses a valid SSL certificate but does not enable modern TLS protocols (TLS 1.2 or 1.3), which is a significant security gap. The lack of security headers such as HSTS, Content-Security-Policy, and X-Frame-Options reduces protection against common web attacks. DNS security features like DNSSEC and CAA are not implemented, increasing risk exposure. No public security policy or incident response contact information is available, which limits transparency and user confidence in handling security incidents. Cookie consent is properly managed via OneTrust, supporting GDPR compliance. Overall, the site is secure enough for general use but requires enhancements to meet higher security standards and regulatory requirements.

Recommendations

  1. Enable TLS 1.2 and TLS 1.3 protocols to improve encryption security.
  2. Implement HTTP security headers including HSTS with preload, Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Configure DNSSEC and CAA records to enhance DNS security and certificate issuance control.
  4. Publish a clear security policy and provide incident response contact channels such as security@ or abuse@ emails.
  5. Enhance mobile optimization and site performance to improve user experience and accessibility.
Technical notes

Notes

The website is built using standard web technologies including HTML5, CSS3, and JavaScript with jQuery. It integrates OneTrust for cookie consent management and uses a valid SSL certificate issued by GlobalSign RSA OV SSL CA 2018. However, the site does not support modern TLS protocols and lacks security headers, which are critical for protecting users. Performance metrics indicate a slow load time (~10.8 seconds) and moderate resource count, suggesting potential optimization opportunities. Mobile and accessibility features are basic, with some responsive CSS but limited advanced enhancements. Hosting appears to be managed by LexisNexis infrastructure. The site uses external domains for analytics, cookie management, and support resources, reflecting a typical enterprise web environment.
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

Reviews of this site

Share your experience with nexis.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 nexis.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.