Skip to main content

Security report for ou.edu

University of Oklahoma College of Law · Education · United States

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

71/100

Risk levelMedium

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

The University of Oklahoma College of Law website presents a comprehensive and professional digital presence for a premier public law school. It offers detailed information about its academic programs including J.D., LL.M., M.L.S., and Paralegal Studies, emphasizing innovation, student support, and practical legal training. The site targets prospective and current law students, legal professionals, and alumni, positioning itself as a leader in legal education with a strong tradition and modern digital initiatives. Technically, the website is built on Drupal 10, leveraging modern JavaScript libraries and marketing tools such as Google Tag Manager and AdRoll for analytics and advertising. The site is mobile-optimized, accessible, and well-structured, providing a positive user experience. Security posture is good with HTTPS enforced and cookie consent mechanisms in place, though it lacks explicit security headers and published security policies. The WHOIS data for the domain law.ou.edu is unavailable due to it being a subdomain under ou.edu, which explains the absence of registrar and registrant information. This is consistent with university domain management practices and does not indicate suspicious activity. Overall, the site is trustworthy, secure, and compliant with privacy regulations. Strategic recommendations include enhancing security transparency by publishing security policies and incident response contacts, implementing security headers, and adding a vulnerability disclosure policy to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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 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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Domain Expires Soon

      Domain expires in 7 days

      What to do: Renew domain registration before expiration

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

Keep watching ou.edu

This scan found 22 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
57
Security headers
50
Email security
80
DNS health
70
Network security
100
GDPR outside view
68
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

Technical appendix

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

Business context

Business profile

The OU College of Law operates as a large educational institution within the public university sector, focusing on legal education and scholarship. Its market position is strong as a premier public law school with innovative programs and a commitment to student success. The business model centers on delivering academic programs, experiential learning, and career development services. Revenue streams likely include tuition, grants, and donations. The institution maintains a broad partnership ecosystem including university-wide resources and external legal communities. Growth indicators include digital initiatives and expanded program offerings. The website reflects a mature, well-established operation with consistent branding and active engagement with its audience.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and cookie consent implemented, indicating compliance with privacy laws such as GDPR. However, the absence of security headers like Content-Security-Policy and lack of publicly available security policies or incident response contacts represent gaps. No vulnerabilities or exposed sensitive data were detected in the HTML content. The use of third-party marketing and analytics tools introduces moderate tracking but is managed with user consent. Overall, the security maturity is good but could be improved with enhanced transparency and technical controls.

Recommendations

  1. Publish a formal security policy and incident response contact information on the website.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a vulnerability disclosure or security.txt file to facilitate responsible reporting.
  4. Review and minimize third-party tracking scripts to enhance user privacy.
  5. Maintain regular security audits and update CMS and libraries to mitigate vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
University of Oklahoma College of Law
Description
The University of Oklahoma College of Law is committed to excellence in educating legal professionals, advancing legal scholarship, and serving the public. OU Law delivers exceptional value through academic rigor, affordability, and outstanding student outcomes.
Key services
J.D. Program, LL.M. Program, M.L.S. Program, Paralegal Studies Program, Legal Clinics, Externships, Career Development
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, jQuery, AdRoll, Google Tag Manager, Capture Higher Ed, Accessible Slick Carousel
Frameworks
Drupal CMS
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via GTM), Capture Higher Ed
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
AdRoll
Tracking pixels
AdRoll, Google Analytics (via GTM)
Marketing tools
Capture Higher Ed
Transparency
good

Site quality

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

Key observations

  1. Website is a professionally maintained educational institution site for OU College of Law.
  2. Content is rich, well-structured, and includes detailed program information.
  3. Multiple programs and student resources are highlighted.
  4. Social media presence is active and linked.
  5. Cookie consent and privacy policy are implemented.
  6. No security policy or incident response info publicly available.
  7. No WHOIS data for the subdomain, consistent with subdomain usage under ou.edu.
  8. Use of modern Drupal CMS and multiple marketing/analytics tools.
  9. No signs of malicious or adult content.
Technical notes

Notes

The website is built on Drupal 10 CMS, a modern and widely supported platform, ensuring good maintainability and security updates. It uses jQuery and accessible carousel libraries for UI enhancements, and integrates marketing and analytics tools like AdRoll and Google Tag Manager. The site is mobile-optimized and accessible, with good SEO practices including meta tags and structured navigation. Performance is moderate, likely influenced by multiple external scripts. There is no indication of technical debt or deprecated technologies. Hosting details are not explicitly identified but likely university-managed infrastructure. Opportunities exist to improve security headers and reduce external dependencies for performance gains.
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 ou.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 ou.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.