Skip to main content

Security report for ohsu-psu-sph.org

OHSU-PSU School of Public Health · Education · United States

Medium risk. 5 critical or high findings in Email security, Security headers and 2 other checks.

Security score

70/100

Risk levelMedium

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

The OHSU-PSU School of Public Health is a collaborative academic institution formed by two leading Oregon universities, focusing on educating future public health leaders through community-engaged learning and research. The website serves prospective and current students, faculty, researchers, and public health professionals, offering comprehensive information on degree programs, research initiatives, and community resources. The institution holds a solid regional market position in public health education and research. Technically, the website is built on WordPress with a modern tech stack including analytics and tracking tools, hosted via Akamai, and optimized for mobile devices. Security posture is good with HTTPS and domain protections, but lacks some advanced security headers and DNSSEC. Privacy compliance is weak due to missing explicit privacy and cookie policies. Overall, the site is professional, trustworthy, and content-rich, but could improve compliance and security transparency.

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

5 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

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

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

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

Keep watching ohsu-psu-sph.org

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
77
Security headers
60
Email security
40
DNS health
75
Network security
100
GDPR outside view
68
Average
70

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 school operates in the education and healthcare sectors, targeting students and professionals interested in public health. Its business model is academic and research-focused, with revenue likely from tuition, grants, and donations. The partnership between OHSU and PSU strengthens its competitive advantage. The website reflects a mature digital presence with integration of marketing and analytics tools, indicating active engagement and outreach. The absence of explicit privacy and security policies suggests room for compliance improvement. The institution maintains partnerships with local government and community organizations, enhancing its ecosystem and impact.

Security posture

The website enforces HTTPS and uses reputable hosting and DNS providers, with domain registration protected by privacy services. However, DNSSEC is not enabled, and several important security headers are missing. There is no visible vulnerability disclosure or incident response information, which could hinder security incident management. The use of multiple tracking and analytics services without clear consent mechanisms raises privacy concerns. Overall, the security posture is moderate but would benefit from enhanced DNS security, published policies, and improved header configurations.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  3. Implement a cookie consent banner/mechanism to comply with privacy regulations.
  4. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and Referrer-Policy.
  5. Establish and publish a vulnerability disclosure policy and incident response contact information.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OHSU-PSU School of Public Health
Description
Two of Oregon’s leading universities, OHSU & PSU, have joined forces to train the next generation of public health leaders. Focus on community-engaged learning and scholarship to address public health problems and educate diverse students.
Key services
Public health degree programs (undergraduate, graduate, doctoral), Research and publications, Student resources and advising, Community engagement and social justice initiatives
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.2, PHP, JavaScript, Google Analytics, Google Tag Manager, HubSpot scripts, Hotjar, Microsoft Clarity, FontAwesome, Google Fonts (Quicksand, Montserrat), Ninja Forms plugin, Events Calendar Pro plugin
Frameworks
WordPress CMS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited and other EPP protections
  • Use of privacy protection for WHOIS
  • No exposed emails in clear text (obfuscated in scripts)

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Hotjar, Microsoft Clarity, HubSpot Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Hotjar, Microsoft Clarity, HubSpot
Marketing tools
HubSpot
Transparency
basic

Site quality

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

Key observations

  1. Website is a professionally maintained academic site for a joint public health school
  2. Content is rich with educational, research, and community engagement information
  3. No explicit privacy or cookie policies found, which is a compliance gap
  4. Use of multiple analytics and tracking tools without visible consent mechanism
  5. No visible security.txt or incident response contact information
  6. Domain registration is privacy protected but justified and consistent
  7. No WAF or blocking detected, full content accessible
Technical notes

Notes

The website is built on WordPress 6.8.2, using standard plugins for forms, events, and analytics. It leverages Google Analytics, Google Tag Manager, HubSpot, Hotjar, and Microsoft Clarity for tracking and marketing. The site uses Google Fonts and FontAwesome for styling and icons. Hosting is via Akamai CDN and OHSU DNS servers, providing good performance and availability. The site is mobile optimized and SEO friendly with proper meta tags and structured data (JSON-LD). Some technical debt is noted in missing security headers and lack of DNSSEC. Overall, the technical infrastructure is solid but can be modernized with enhanced security and privacy features.
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 ohsu-psu-sph.org. 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 ohsu-psu-sph.org.

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.