Skip to main content

Security report for orsymphony.org

Oregon Symphony · Other · United States

Low risk. No critical or high findings.

Security score

86/100

Risk levelLow

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

Oregon Symphony is a well-established regional symphony orchestra with a long history dating back to 1896. The organization offers world-class concerts primarily serving the Portland and Salem, Oregon areas. Their website serves as the official source for ticket sales and information about their performances, targeting music enthusiasts and the general public interested in cultural events. The business model is typical of non-profit performing arts organizations, focusing on community engagement and ticketed events. Technically, the website employs modern JavaScript libraries and tracking tools such as Google Tag Manager, Cookiebot for consent management, and Braze for marketing automation. Hosting and DNS are managed via Cloudflare, providing performance and security benefits. The site is mobile-optimized with good SEO practices, though no explicit CMS was detected, suggesting a custom or proprietary platform. From a security perspective, the site uses HTTPS with a good SSL configuration but lacks DNSSEC and security headers, which are recommended for enhanced protection. Cookie consent is implemented, indicating awareness of privacy regulations, but no explicit privacy policy or terms of service were found in the provided content. No vulnerability disclosure or incident response information is published, which could be improved to enhance trust and compliance. Overall, the website is professional, trustworthy, and serves its audience well. Strategic improvements in security headers, DNSSEC, and publishing privacy and security policies would strengthen its security posture and compliance readiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
100/ 100 · Low
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

No critical or high findings. These medium findings are worth fixing next.

  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.

    • Medium

      Missing Permissions-Policy header

      Controls browser features and APIs

      What to do: Implement a Permissions-Policy to restrict feature access

      • OWASP Secure Headers: OWASP Secure Headers Project recommends Permissions-Policy: accelerometer=(), autoplay=(), camera=(), cross-origin-isolated=(),…
  2. 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.

    • Medium

      DMARC not enforcing

      DMARC policy is set to "none"

      What to do: Gradually move to "quarantine" then "reject" policy

    • Medium

      No MTA-STS Policy

      MTA-STS enforces TLS for email delivery

      What to do: Implement MTA-STS to prevent downgrade attacks

  3. DNS health

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

    • Medium

      DNSSEC Not Enabled

      DNSSEC is not configured for this domain

      What to do: Enable DNSSEC to prevent DNS spoofing attacks

      • CAPEC-142
      • RFC 4033
      • RFC 4035
    • Medium

      Domain Transfer Lock Not Enabled

      Domain can be transferred without authorization

      What to do: Enable domain transfer lock for security

Keep watching orsymphony.org

This scan found 15 issues across 5 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
100
Security headers
80
Email security
70
DNS health
65
Network security
100
GDPR outside view
100
Average
86

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

Oregon Symphony holds a strong market position as a regional cultural institution with a legacy since 1896. Its competitive advantage lies in its established brand, community presence, and quality performances. The business model revolves around ticket sales, donations, and community outreach. The target customer segments include local residents, tourists, and classical music aficionados. The organization leverages partnerships with marketing and analytics providers to optimize audience engagement. Growth indicators include digital marketing adoption and modern website infrastructure. The partnership ecosystem includes analytics and consent management vendors but no direct business partners were identified from the domain data.

Security posture

The current security maturity level is moderate. The site enforces HTTPS and uses a reputable DNS provider but lacks DNSSEC and critical security headers such as Content-Security-Policy and X-Frame-Options. No exposed sensitive data or vulnerable libraries were detected. Privacy compliance is partially addressed with cookie consent but lacks a published privacy policy and incident response contacts. The absence of a vulnerability disclosure or security.txt file limits transparency. The organization should prioritize implementing security headers, enabling DNSSEC, and publishing security policies to improve readiness and reduce risk.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a comprehensive privacy policy and terms of service accessible from the website footer.
  4. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Provide clear incident response contact information such as security@ or abuse@ email addresses.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Oregon Symphony
Description
Your official source for Oregon Symphony Tickets. Explore the Oregon Symphony located in Portland and Salem, OR. Join us for one of our world-class concerts.
Key services
Symphony concerts, Ticket sales, Community engagement
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Cookiebot, Cloudflare DNS, Braze SDK, Swiper.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Cookie consent implemented
  • No DNSSEC (not enabled)

Analytics and tracking

Services
Google Analytics, TikTok Analytics, Facebook Analytics, Heatmap.it
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
TikTok Pixel, Facebook Pixel, Heatmap.it
Marketing tools
Braze
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well maintained
  2. Cookie consent is implemented via Cookiebot
  3. No explicit privacy policy or terms of service found in the provided content
  4. Multiple third-party analytics and tracking scripts are used
  5. No direct contact information (email, phone, address) found in the provided HTML snippet
  6. No security.txt or vulnerability disclosure found
  7. No security headers detected in the provided data
  8. Domain is old and registered with a reputable registrar
  9. DNSSEC is not enabled, which is a minor security gap
Technical notes

Notes

The website uses a modern JavaScript-based front end with asynchronous loading of scripts and integration of multiple third-party analytics and marketing tools. Hosting is supported by Cloudflare DNS, enhancing performance and security. The site is mobile responsive and optimized for SEO with appropriate meta tags and Open Graph data. However, no explicit CMS was detected, indicating a custom solution which may require dedicated maintenance. Performance is moderate with room for improvement in loading speed and accessibility features. Technical debt appears low but security enhancements are recommended to reduce risk.
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. 79/100Low26 findingsView report
Reviews of this site

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