Skip to main content

Security report for beamrad.io

Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

66/100

Risk levelMedium

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

Beam Radio is a niche podcast platform focused on the Elixir programming language, Erlang, and the BEAM virtual machine ecosystem. It features a panel of expert hosts and delivers educational and conversational content to developers and enthusiasts interested in functional programming technologies. The business model is content-driven, supported by sponsorships from companies like Grox.io and Underjord. The website is professionally designed, with consistent branding and high-quality content that appeals to its target audience. Technically, the site is built on the Fireside CMS platform, leveraging modern web technologies such as Typekit fonts, FontAwesome icons, and Turbolinks for enhanced user experience. The site is served over HTTPS, ensuring secure communication. Performance and mobile optimization are good, though accessibility features are basic. SEO is well addressed with proper meta tags and Open Graph data. From a security perspective, the site enforces HTTPS and does not expose sensitive data in its HTML content. However, it lacks several security headers that could improve protection against common web attacks. There is no visible privacy policy, cookie consent mechanism, or contact information for security incidents, which are gaps in compliance and user trust. The WHOIS data is unavailable due to privacy protection, which is typical for small content sites and does not raise immediate concerns. Overall, Beam Radio presents a low-risk profile with strong content and technical foundations but would benefit from enhanced privacy compliance and security best practices to improve trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

7 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
    • 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';…

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

    • 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

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

Keep watching beamrad.io

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. The full timeline opens with your unlock code.

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
72
Security headers
50
Email security
70
DNS health
55
Network security
100
GDPR outside view
50
Average
66

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

Beam Radio occupies a specialized segment in the technology podcast market, focusing on the BEAM ecosystem and functional programming languages. Its competitive advantage lies in expert hosts and high-quality, relevant content for a dedicated developer community. Revenue streams appear to be sponsorship-based, with no direct sales or subscription models evident. The target customers are developers and technology enthusiasts interested in Elixir and Erlang. Growth indicators include regular episode releases and partnerships with sponsors. The partnership ecosystem includes Grox.io and Underjord, indicating some industry collaboration. The business operates as a small entity with a focused content strategy and a professional digital presence.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible exposure of sensitive data. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces its defense-in-depth posture. There are no published policies or contact channels for incident response or vulnerability disclosure, which limits transparency and readiness. Compliance with GDPR and other privacy regulations is weak due to missing privacy and cookie policies. The security culture appears informal, typical for small content sites, but improvements in policy publication and security headers would enhance resilience and trust.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance and user trust.
  2. Add essential security headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) to strengthen protection against common web attacks.
  3. Provide clear contact information for business inquiries and security incident reporting to enhance transparency and responsiveness.
  4. Consider publishing a security.txt file to facilitate vulnerability disclosure and improve security posture.
  5. Regularly review and update technical infrastructure to maintain performance, accessibility, and security standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A podcast featuring stories and conversations around Elixir, Erlang and the BEAM ecosystem with a panel of experts.
Key services
Podcast episodes, Interviews with experts, Educational content on Elixir and Erlang
Content quality
excellent
Branding
consistent

Technology

Stack
Fireside CMS, Typekit fonts, FontAwesome icons, Turbolinks, HTTPS
Frameworks
Fireside 2.1
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a professionally produced podcast site focused on Elixir and BEAM ecosystem.
  2. No WHOIS data publicly available, indicating privacy protection.
  3. No explicit privacy, cookie, or terms of service policies found on the main page.
  4. No contact emails or phone numbers found in the HTML content.
  5. No security.txt or vulnerability disclosure information present.
  6. Site uses HTTPS and modern web technologies with good design and navigation.
  7. External links mostly to podcast platforms and media hosting domains.
  8. No signs of WAF or content blocking detected.
Technical notes

Notes

The website is built using the Fireside CMS platform, which is specialized for podcast hosting and publishing. It uses modern front-end technologies including Typekit for fonts and FontAwesome for icons, enhancing visual appeal and usability. Turbolinks is employed to improve navigation speed and user experience. The site is served over HTTPS, indicating good baseline security. Performance is moderate, with good mobile optimization but only basic accessibility features. SEO is well implemented with proper meta tags and Open Graph data. There is no evidence of technical debt or outdated libraries in the provided HTML content. Hosting provider details are not explicitly found but likely related to Fireside's infrastructure.
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 beamrad.io. 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 beamrad.io.

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.