Skip to main content

Security report for kboo.fm

KBOO · Media · United States

Medium risk. 7 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

53/100

Risk levelMedium

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

KBOO is a well-established community radio station based in Portland, Oregon, providing alternative media content and community engagement since at least 2002, with roots dating back to 1968. The station operates as a non-profit entity, funded primarily through donations, memberships, underwriting, and volunteer support. Its website serves as a hub for live streaming, program schedules, community involvement, and donation facilitation, targeting local community members and alternative media audiences. Technically, the site runs on Drupal 7 with Bootstrap and jQuery, integrating analytics tools like Google Analytics and Matomo, and includes social media and donation platform integrations. While the site is functional and well-structured with good content quality and navigation, it uses an outdated CMS version, lacks a cookie consent mechanism, and does not enable DNSSEC, which are areas for improvement. Security posture is moderate with HTTPS enforced and some security best practices observed, but could be enhanced by upgrading the CMS, enabling DNSSEC, and implementing stronger security headers. Overall, the website is trustworthy and professional, with clear business legitimacy and community focus.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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. 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

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  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 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
    • 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 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

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

Keep watching kboo.fm

This scan found 21 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
40
Email security
60
DNS health
80
Network security
100
GDPR outside view
35
Average
53

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

KBOO holds a strong position as a niche community radio station with a loyal local audience. Its business model relies on community funding and volunteerism, supported by a clear online presence that encourages donations and participation. The integration with donation platforms and merchandise sales partners indicates diversified revenue streams. The station's long domain age and transparent WHOIS data reinforce its credibility. The website's content and navigation support user engagement effectively, though modernization of technical infrastructure would support future growth and security. Partnerships with donation processors and merchandise platforms are strategic for sustaining operations.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and clientTransferProhibited domain status. However, the use of Drupal 7, which is no longer supported, introduces potential vulnerabilities. The absence of DNSSEC reduces DNS security, and missing explicit security headers like CSP and X-Frame-Options are gaps. No incident response or security policy information is published, limiting transparency in security governance. Tracking scripts are used responsibly with DoNotTrack enabled in Matomo, but lack of cookie consent may pose compliance risks. Overall, the security posture is adequate for a small non-profit but requires improvements to mitigate risks.

Recommendations

  1. Upgrade the website CMS from Drupal 7 to a supported and secure version to reduce vulnerability exposure.
  2. Implement DNSSEC to enhance domain name system security and prevent DNS spoofing.
  3. Add a cookie consent banner/mechanism to comply with privacy regulations and improve user transparency.
  4. Publish a formal security policy and incident response contact information to improve trust and compliance.
  5. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
KBOO
Description
Community radio station serving Portland, Oregon and surrounding areas, providing alternative media content and community engagement.
Key services
Live radio streaming, On-air programming, Community event sponsorship, Volunteer opportunities, Donations and membership drives
Content quality
good
Branding
consistent

Technology

Stack
Drupal 7, Bootstrap, jQuery 2.2, Google Analytics, Matomo Analytics, ShareThis, Olark Live Chat
Frameworks
Drupal
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • No exposed sensitive data in HTML
  • Use of analytics with DoNotTrack enabled in Matomo

Analytics and tracking

Services
Google Analytics, Matomo
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Matomo, ShareThis
Marketing tools
ShareThis
Transparency
basic

Site quality

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

Key observations

  1. Website uses Drupal 7 CMS which is outdated and may pose security risks.
  2. No explicit privacy cookie consent mechanism found despite use of tracking scripts.
  3. WHOIS data is transparent and consistent with website content.
  4. Website provides comprehensive community radio content and engagement opportunities.
  5. Multiple social media and donation platforms integrated.
  6. No evidence of phishing, malware, or suspicious content.
Technical notes

Notes

The website is built on Drupal 7 CMS with Bootstrap and jQuery libraries, integrating Google Analytics, Matomo, ShareThis, and Olark live chat for enhanced user engagement and analytics. The site uses responsive design and includes meta tags for SEO and social media sharing (Open Graph, Twitter cards). Hosting details are not explicit but DNS is managed via EasyDNS and domain registered with Gandi SAS. Performance is moderate with multiple CSS and JS files loaded asynchronously. Accessibility is basic with some ARIA and semantic HTML elements. The site lacks modern security headers and cookie consent mechanisms. Overall, the technical infrastructure supports the business needs but requires modernization and security enhancements.
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 kboo.fm. 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 kboo.fm.

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.