Skip to main content

Security report for ohs.org

Oregon Historical Society · Non-profit · United States

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

Security score

70/100

Risk levelMedium

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

The Oregon Historical Society is a well-established non-profit organization dedicated to preserving and sharing Oregon's rich history through its museum, research library, educational programs, and digital content. The website reflects a mature digital presence with comprehensive content targeting historians, educators, researchers, and the general public interested in Oregon's cultural heritage. The organization maintains a strong market position as the state's collective memory with over a century of history and a large collection of artifacts and archival materials. Technically, the website is built on the CommonSpot CMS platform and employs modern web technologies including Google Analytics for tracking and Adobe Typekit for fonts. The site is mobile-optimized and accessible, with good SEO practices and clear navigation. Performance is moderate, with room for optimization. From a security perspective, the site enforces HTTPS and includes anti-clickjacking measures. However, explicit security headers like Content-Security-Policy are not clearly present, and there is no visible security or incident response policy published. Privacy compliance is partial; a privacy policy is present and comprehensive, but cookie consent mechanisms are lacking, which may pose GDPR compliance risks. Overall, the website is trustworthy and professional, with strong business credibility and content quality. The main risk areas include privacy compliance enhancements and formalizing security policies. The absence of WHOIS data limits domain registration trust verification but does not detract significantly from the site's legitimacy.

Scanned

NIS2 and GDPR posture

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

  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

  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

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

Keep watching ohs.org

This scan found 23 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
62
Security headers
45
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
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 Oregon Historical Society operates as a non-profit cultural institution with a focus on education, preservation, and public engagement. Its revenue streams likely include memberships, donations, event ticket sales, and grants. The organization targets a broad audience including educators, researchers, historians, and the general public interested in Oregon history. The website's partnerships with related digital history projects and encyclopedias strengthen its ecosystem and outreach. The presence of volunteer and employment opportunities indicates organizational growth and community involvement. The business model emphasizes accessibility and educational impact rather than commercial profit.

Security posture

The website demonstrates a moderate to good security posture with HTTPS enforced and anti-clickjacking scripts implemented. No sensitive data is exposed in the HTML content, and forms use POST methods for data submission. However, the lack of explicit security headers such as Content-Security-Policy and absence of a published security or incident response policy are gaps. There is no visible vulnerability disclosure or security.txt file, which could hinder coordinated vulnerability reporting. Privacy compliance is partial, with no cookie consent banner detected, potentially exposing the organization to GDPR compliance risks. Overall, the security maturity is adequate for a non-profit but could be improved with formal policies and enhanced header configurations.

Recommendations

  1. Implement and publish a comprehensive security policy and incident response plan on the website.
  2. Add explicit Content-Security-Policy and other recommended security headers to enhance protection.
  3. Deploy a cookie consent mechanism to ensure GDPR and privacy regulation compliance.
  4. Create and publish a security.txt file to facilitate vulnerability disclosure and improve security transparency.
  5. Regularly audit third-party scripts and tracking tools to minimize security risks and improve privacy compliance.

Contact details published on the site

Addresses
Legal name
Oregon Historical Society
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Oregon Historical Society
Description
The Oregon Historical Society is dedicated to putting the power of Oregon’s rich, surprising history into everyone’s hands. For more than a century, it has served as the state’s collective memory, gathering and preserving historical pieces including over 85,000 artifacts and millions of photographs, films, and manuscripts, and sharing them through its museum, research library, academic journal, educational programs, and digital content.
Key services
Museum exhibits, Research library access, Educational programs, Digital history projects, Publication of Oregon Historical Quarterly, Events and lectures
Content quality
excellent
Branding
consistent

Technology

Stack
CommonSpot CMS, Google Analytics, Typekit Fonts, RequireJS, SVG icons
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Anti-clickjacking script present
  • No exposed sensitive data in HTML
  • Secure form submission via POST

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

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 no blocking detected.
  2. WHOIS data is unavailable or malformed, limiting domain registration insights.
  3. Strong presence of educational and cultural content with multiple exhibits and events.
  4. Clear contact information and social media presence enhance trust.
  5. No explicit privacy or cookie consent banners detected, potential GDPR compliance gap.
  6. Use of CommonSpot CMS and modern web technologies.
  7. Security best practices mostly followed but could improve with explicit headers and policies.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website uses CommonSpot CMS, a mature content management system, combined with modern frontend technologies such as SVG icons, RequireJS, and Adobe Typekit fonts. Google Analytics and Google Tag Manager are used for analytics and marketing tracking. The site is mobile responsive and accessible, with good SEO metadata including Open Graph tags. Performance is moderate, with potential improvements in resource loading and caching. The absence of explicit hosting provider information limits full infrastructure assessment. Overall, the technical implementation is solid but could benefit from performance tuning and enhanced security header deployment.
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 ohs.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 ohs.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.