Skip to main content

Security report for northwestern.edu

Northwestern University · Education · United States

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

Security score

71/100

Risk levelMedium

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

Northwestern University is a prestigious large educational institution in the United States, offering a wide range of undergraduate, graduate, and professional programs across multiple disciplines. It holds a strong market position as a top-ranked national university with recognized graduate schools and a focus on interdisciplinary research and innovation. The website reflects a mature digital presence with excellent design, navigation, and content quality, targeting students, faculty, alumni, and the broader community. Technically, the site uses Apache server technology, jQuery, and Google Tag Manager for analytics, with a valid SSL certificate but lacks modern TLS protocol support and some advanced security headers. Security posture is moderate with room for improvement in encryption protocols, HSTS implementation, and domain security features. Privacy compliance is basic with a comprehensive privacy policy but no visible cookie consent mechanism. Overall, the site is professional and trustworthy but could enhance security and compliance to reduce risk and improve user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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 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 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

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

Keep watching northwestern.edu

This scan found 18 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
85
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
43
Average
71

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention northwestern.edu, from OffSeq Breach.

Total records
12,997
Employees
317
Customers
7,066
Third parties
5,614
Weak passwords
8%

Latest record dated 2026-06-13 · 363 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for northwestern.edu.

Select it in the checkout above.

Masked preview

  • –ads-fed.northwestern.edu2026-06-13
  • –websso.it.northwestern.edu2026-06-12
  • –websso.it.northwestern.edu2026-06-08
  • –ads-fed.northwestern.edu2026-06-06
  • –www-cambridge-org.turing.library.northwestern.edu2026-06-06

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

Northwestern University operates as a non-profit educational entity focused on delivering high-quality education and research services. Its competitive advantages include top-tier graduate schools, interdisciplinary research centers, and strong community engagement. The business model centers on tuition, research funding, and philanthropic giving. The university targets prospective and current students, faculty, staff, alumni, and media. Partnerships with various internal and external entities support its ecosystem. The website content and structure indicate a strategic emphasis on innovation, diversity, and global engagement. Growth indicators include recent news on research initiatives and sustainability programs. The marketing ecosystem includes multiple verification and marketing tools, reflecting active digital outreach.

Security posture

The current security maturity level is moderate. The site employs basic security headers such as X-Frame-Options and secure, HttpOnly cookies, and holds a valid SSL certificate issued by a reputable CA. However, the absence of TLS 1.2 or higher protocols, lack of HSTS, and missing DNSSEC and CAA records indicate gaps in domain and transport security. No published security policy or incident response contacts were found, which limits transparency and readiness. GDPR compliance is partial, with a privacy policy present but no cookie consent mechanism. The site shows no known vulnerabilities like Heartbleed or POODLE. Overall, the security posture is adequate for a university website but requires enhancements to meet higher standards and regulatory requirements.

Recommendations

  1. Enable and enforce TLS 1.2 or TLS 1.3 protocols to secure data in transit.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Deploy DNSSEC and CAA records to protect domain integrity and certificate issuance.
  4. Publish a comprehensive security policy and provide clear incident response contact information.
  5. Add a cookie consent mechanism to comply with GDPR and enhance user privacy transparency.

Contact details published on the site

Addresses
Legal name
Northwestern University
Technical notes

Notes

The website infrastructure is based on Apache server technology with client-side JavaScript libraries including jQuery and Mmenu.js for UI components. Google Tag Manager is used for analytics and marketing tracking. The site uses multiple CSS stylesheets hosted on common.northwestern.edu, indicating centralized asset management. Performance is fast with no resource or page size issues reported. Mobile optimization and accessibility are good, supported by responsive design and ARIA attributes. SEO is well addressed with canonical links and Open Graph metadata. However, the SSL configuration lacks modern protocol support, which is a technical risk. The absence of a detected CMS suggests a custom or proprietary platform. Hosting provider details are not explicit but likely internal or university-managed. Overall, the technical stack is stable and mature but could benefit from modernization in security protocols.
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 northwestern.edu. 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 northwestern.edu.

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.