Skip to main content

Security report for podlove.org

Podlove · Technology · N/a

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

Security score

52/100

Risk levelMedium

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

Podlove is an open-source project providing Wordpress plugins and tools for podcast publishing, enabling users to self-host their podcasts with full control over content. The website positions itself as a niche provider in the podcasting technology space, emphasizing independence from third-party hosting. Technically, the site is built using modern web technologies including React, Gatsby, and Tailwind CSS, delivering good performance and mobile optimization. Security posture is solid with HTTPS enabled and domain transfer protections, though improvements such as enabling DNSSEC and adding security headers are recommended. Privacy compliance is partially addressed with a privacy policy present, but lacks a cookie consent mechanism. Overall, the site is trustworthy and professional, with a strong community and open-source ethos.

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

6 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 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 podlove.org

This scan found 25 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
65
Security headers
15
Email security
70
DNS health
70
Network security
40
GDPR outside view
53
Average
52

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

Podlove operates in the technology and media sectors, targeting podcasters and Wordpress users seeking open-source podcast publishing solutions. Its business model relies on community support and donations rather than commercial hosting services. The project has been active since 2012, indicating maturity and stability. The presence of testimonials and open-source code on GitHub enhances credibility. The ecosystem includes multiple podcasting tools such as a web player and subscribe button, catering to a comprehensive podcast publishing workflow. External links to partner podcasts and community forums suggest an engaged user base and collaborative environment.

Security posture

The website demonstrates a good security baseline with HTTPS enforced and domain registration protections like clientTransferProhibited status. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options represents areas for enhancement. No vulnerabilities or exposed sensitive data were detected in the HTML content. The lack of a published security policy or incident response contact channels limits transparency in security governance. No analytics or tracking scripts were found, reducing privacy risks. Overall, the security posture is adequate for the site's purpose but could benefit from formalized policies and technical hardening.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers (CSP, X-Frame-Options, HSTS) to mitigate common web attacks.
  3. Add a cookie consent banner or mechanism to comply fully with GDPR and enhance user privacy transparency.
  4. Publish a dedicated security policy and incident response contact information to improve trust and readiness.
  5. Consider providing direct contact emails or phone numbers for business and support inquiries to improve accessibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Podlove
Description
Podlove is a group of Wordpress plugins that allow users to self-host podcasts, providing tools for podcast publishing, web player integration, and subscription buttons. It emphasizes open, independent internet and full content control without third-party hosting.
Key services
Podlove Publisher Wordpress plugin, Podlove Web Player, Podcast Subscribe Button
Content quality
good
Branding
consistent

Technology

Stack
React, Gatsby, Tailwind CSS, HTML5, JavaScript
Frameworks
Gatsby
Platforms
Wordpress (for plugins)
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on podcast publishing tools and open source software.
  3. No direct contact emails or phone numbers found; contact is via a contact page form.
  4. No cookie consent mechanism detected despite GDPR compliance indications.
  5. No explicit security policy or incident response information published.
  6. No analytics or tracking scripts detected in HTML content.
  7. Website uses modern technologies and frameworks with good performance and mobile optimization.
  8. WHOIS data shows domain is well maintained and not privacy protected.
Technical notes

Notes

The website is built on a modern React-based static site generator (Gatsby) with Tailwind CSS for styling, ensuring responsive and performant user experience. The use of Wordpress plugins for core podcast publishing functionality indicates a hybrid technical ecosystem. Hosting is managed by http.net Internet GmbH, a reputable registrar. The site loads efficiently with preloaded scripts and optimized assets. Accessibility is basic but functional, with room for improvement in semantic markup and ARIA roles. SEO is supported by proper meta tags and structured navigation. No analytics or third-party trackers were detected, aligning with privacy-conscious design.
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 podlove.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 podlove.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.