Skip to main content

Security report for jhu.edu

Johns Hopkins University · Education · United States

Medium risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

50/100

Risk levelMedium

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

Johns Hopkins University is a prestigious and long-established research university founded in 1876, offering a wide range of undergraduate, graduate, and professional education programs. The institution is recognized for its strong academic divisions, research initiatives, and community engagement. The website serves as a comprehensive portal for prospective students, faculty, alumni, and the public, providing detailed information about academics, admissions, research, and campus life. The university maintains a consistent and professional brand presence across its digital assets and social media channels. Technically, the website is built on WordPress and integrates modern marketing and analytics tools such as Google Tag Manager, Facebook Pixel, and Twitter tracking. However, the site suffers from significant security shortcomings, notably the absence of HTTPS/SSL encryption, lack of security headers, and no support for modern TLS protocols. Performance is also a concern, with slow page load times and a large page size impacting user experience. Privacy compliance is partially addressed with a comprehensive privacy policy, but the lack of a cookie consent mechanism is a gap. From a security perspective, the site’s lack of HTTPS is a critical vulnerability that undermines user trust and data protection. While DMARC is properly configured with a reject policy, other security best practices such as HSTS, DNSSEC, and OCSP stapling are missing. The WHOIS data confirms the domain’s legitimacy and consistency with the university’s identity, supporting a high trustworthiness rating. Overall, Johns Hopkins University’s website is content-rich and professionally designed but requires urgent improvements in security infrastructure and performance optimization to meet modern standards and protect its users effectively.

Scanned

This is an earlier scan of jhu.edu. View the latest report

NIS2 and GDPR posture

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

7 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  2. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching jhu.edu

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
0
Security headers
65
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
50

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

Johns Hopkins University holds a leading position in the higher education sector, particularly in research and medical education. Its business model focuses on delivering high-quality education and research outputs, supported by a large and diverse academic community. The university leverages partnerships with affiliated medical and research institutions to enhance its offerings. Revenue streams likely include tuition, research grants, donations, and endowments. The target audience spans prospective students, researchers, faculty, alumni, and the general public. The university’s extensive use of digital channels and social media indicates a mature digital presence aimed at engagement and outreach. Strategic observations include the need to modernize technical infrastructure and enhance security to maintain competitive advantage and trust.

Security posture

The current security posture of the Johns Hopkins University website is weak due to the absence of HTTPS/SSL, which is a fundamental security requirement. The lack of security headers and modern TLS support further exposes the site to potential attacks such as man-in-the-middle and protocol downgrade attacks. Although DMARC is configured with a strict reject policy, other DNS security features like DNSSEC are not enabled. No explicit incident response or vulnerability disclosure policies are found on the site, which could hinder timely handling of security incidents. The use of reputable analytics and marketing tools is noted, but care should be taken to ensure these do not introduce privacy risks. Overall, the site requires immediate remediation of critical security gaps to protect user data and institutional reputation.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS across the entire site.
  2. Enable HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Activate HSTS with includeSubDomains and preload to prevent protocol downgrade attacks.
  4. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  5. Introduce a cookie consent mechanism to comply with privacy regulations and improve user transparency.
  6. Optimize website performance by reducing page size and improving load times.
  7. Establish and publish a vulnerability disclosure policy and incident response contact information.
  8. Regularly audit third-party scripts and libraries for vulnerabilities and privacy compliance.
  9. Enhance accessibility features to maintain compliance with standards and improve user experience.
  10. Maintain consistent updates to WHOIS and domain registration information to ensure trust.

Contact details published on the site

Addresses
Technical notes

Notes

The website is powered by WordPress CMS and integrates multiple third-party analytics and marketing tools such as Google Tag Manager, Facebook Pixel, and Twitter tracking scripts. The site uses modern JavaScript libraries including jQuery, Backbone, and Lodash. Despite this, the site lacks HTTPS support and does not enable any TLS protocols, which is a critical technical deficiency. The page load time is very slow (~20 seconds) with a large number of resources (306) and a page size exceeding 1MB, indicating potential technical debt and optimization opportunities. The site is mobile optimized and includes accessibility features, but performance and security shortcomings overshadow these positives. Hosting appears to be managed internally or via a dedicated provider associated with the university's IP range. Overall, the technical infrastructure requires modernization and security hardening to align with best practices.
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. 75/100Medium29 findingsView report
Reviews of this site

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