Skip to main content

Security report for uchicago.edu

The University of Chicago · Education · United States

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

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

The University of Chicago website represents a leading global research university offering comprehensive educational programs, research initiatives, and community engagement. The site targets students, faculty, staff, alumni, and the broader public, providing clear navigation to admissions, academic departments, campus life, and global impact. The university maintains a strong market position as a prestigious educational institution with a large scale and extensive services. Technically, the website is built on a modern React framework with Sitecore CMS, leveraging Azure CDN for hosting and performance. It integrates analytics tools such as Hotjar and Google Tag Manager for user behavior tracking and marketing insights. The site demonstrates good mobile optimization, accessibility, and SEO practices, contributing to an excellent user experience. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. However, it lacks explicit security headers and a public vulnerability disclosure policy. Privacy compliance is supported by a comprehensive privacy policy and GDPR adherence, though a cookie consent mechanism is not evident. Contact information is available primarily through forms and linked pages rather than direct emails or phone numbers. Overall, the website is professional, trustworthy, and well-maintained, with minor areas for improvement in security headers and privacy consent mechanisms. The absence of WHOIS data is typical for .edu domains and does not detract from the site's legitimacy. Strategic recommendations include enhancing security headers, publishing incident response contacts, and implementing cookie consent to strengthen compliance and user trust.

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

6 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 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 uchicago.edu

This scan found 21 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
90
Security headers
20
Email security
75
DNS health
65
Network security
100
GDPR outside view
58
Average
68

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

The University of Chicago operates as a large educational institution focused on undergraduate, graduate, and continuing education, alongside world-class research and community impact. Its competitive advantages include a strong academic reputation, diverse program offerings, and global reach. Revenue streams likely include tuition, research grants, donations, and medical services via UChicago Medicine. The target customer segments encompass prospective and current students, faculty, researchers, alumni, and community partners. Growth indicators include active news, events, and outreach programs. The university maintains partnerships with various internal and external entities, reflected in multiple linked domains and social media channels. Operationally, the institution emphasizes intellectual freedom, diversity, and inclusion, aligning with its mission and market positioning.

Security posture

The website exhibits a mature security posture with enforced HTTPS and no visible exposure of sensitive data. The use of modern frameworks and asynchronous loading of analytics scripts reduces risk. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options represents an area for enhancement. No vulnerabilities or malware indicators were detected in the content. Privacy compliance is supported by a detailed privacy policy and GDPR adherence, but the lack of a cookie consent mechanism and public incident response contacts limits transparency. The site would benefit from publishing a vulnerability disclosure policy and security.txt file to improve security culture and incident readiness. Overall, the security posture is strong but could be improved with additional best practices and transparency.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  2. Add a clear cookie consent banner to comply with GDPR and enhance user privacy transparency.
  3. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting and incident response.
  4. Provide public contact information for security incidents to improve trust and readiness.
  5. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
The University of Chicago
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
The University of Chicago
Description
One of the world’s leading research universities, the University of Chicago inspires scholars to pursue field-defining research, while providing a transformative education for students.
Key services
Undergraduate and graduate education, Research and scholarship, Community and global impact initiatives, Campus resources and student life, Medical services via UChicago Medicine
Content quality
excellent
Branding
consistent

Technology

Stack
React (data-react-helmet tags), Bootstrap 5, Hotjar (user behavior analytics), Google Tag Manager, Azure CDN (cdn-endpoint.azureedge.net), Typekit fonts
Frameworks
React
Platforms
Azure CDN
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager and Hotjar with async loading

Analytics and tracking

Services
Hotjar, Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Hotjar
Marketing tools
Hotjar
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and navigation.
  2. No WAF or blocking mechanisms detected.
  3. Strong branding and consistent user experience.
  4. Comprehensive educational content and resources.
  5. No direct company contact emails or phone numbers found in HTML; contact via forms and pages.
  6. No explicit cookie consent banner detected despite tracking scripts.
  7. WHOIS data unavailable, typical for .edu domains with restricted WHOIS access.
Technical notes

Notes

The website is built on a modern React-based front end integrated with Sitecore CMS, hosted on Microsoft Azure CDN infrastructure. It uses Bootstrap 5 for responsive design and Typekit for fonts, ensuring good mobile optimization and accessibility. Analytics and marketing tools include Hotjar and Google Tag Manager, loaded asynchronously to optimize performance. The site demonstrates good SEO practices with appropriate meta tags and Open Graph data. Performance is moderate, with potential for improvement through optimization of third-party scripts and caching strategies. The technical stack is modern and well-maintained, supporting a professional and user-friendly experience.
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. 68/100Medium29 findingsView report
Reviews of this site

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