Skip to main content

Security report for plyr.io

Plyr · Technology · Australia

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

Security score

58/100

Risk levelMedium

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

Plyr.io is a specialized website offering a simple, customizable HTML5 media player supporting video, audio, YouTube, and Vimeo content. The project is open source, hosted on GitHub with a significant community presence (29K stars), indicating strong market interest and adoption among developers and content creators. The business operates primarily in the technology sector, focusing on media playback solutions with accessibility and customization as key features. The company behind the site is registered in Australia and has maintained the domain since 2015, reflecting a mature and stable presence in its niche. Technically, the website employs modern web standards including HTML5, CSS3, and JavaScript, with SVG icons and integration of Google Analytics and Tag Manager for user tracking. Hosting and domain registration are managed via Cloudflare, ensuring robust infrastructure and fast performance. The site is mobile optimized and accessible, with good SEO practices evident from meta tags and Open Graph data. However, no CMS or major frameworks are detected, suggesting a lightweight custom implementation. From a security perspective, the site benefits from HTTPS and Cloudflare's DNS and registrar services, but lacks DNSSEC and explicit security headers such as Content-Security-Policy or X-Frame-Options. There is no visible privacy policy, cookie consent mechanism, or terms of service, which are critical for GDPR and privacy compliance. No contact information or incident response channels are provided, limiting transparency and user trust in security matters. The absence of a vulnerability disclosure policy or security.txt file further reduces the security posture. Overall, Plyr.io presents a professional and trustworthy front for its open source media player project with high content and technical quality. The main risks relate to privacy compliance and security best practices, which could be improved by publishing relevant policies, enabling DNSSEC, and adding security headers. Strategic recommendations include enhancing privacy transparency, establishing incident response contacts, and improving security configurations to align with industry standards.

Scanned

This is an earlier scan of plyr.io. View the latest report

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

9 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 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 plyr.io

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
20
Email security
70
DNS health
55
Network security
100
GDPR outside view
35
Average
58

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

Plyr.io occupies a niche market as a provider of customizable HTML5 media players, targeting developers, content creators, and web professionals who require accessible and flexible media playback solutions. The open source business model leverages GitHub for distribution and community engagement, with a strong reputation evidenced by a large star count. Revenue streams are likely indirect, possibly through donations, sponsorships, or consulting. The company is small, focused on technology, and operates from Australia. The partnership ecosystem includes integration with major platforms like YouTube and Vimeo, enhancing its utility. The lack of direct contact information or formal business disclosures suggests a lean operation focused on software development rather than commercial sales. Growth indicators include ongoing updates and community contributions. Strategic observations highlight the importance of improving compliance and security transparency to support broader adoption and trust.

Security posture

The security maturity of Plyr.io is moderate. The site uses HTTPS and Cloudflare services, providing a solid foundation for secure communications and domain management. However, the absence of DNSSEC and security headers indicates gaps in defense-in-depth strategies. No sensitive data exposure or vulnerable libraries were detected in the provided content. The lack of privacy and cookie policies, as well as missing incident response contacts, represent compliance and operational risks, especially under GDPR and similar regulations. The use of Google Analytics and Tag Manager introduces moderate user tracking without visible consent mechanisms, which could lead to privacy concerns. Overall, the security culture appears minimal but functional, with room for improvement in transparency, policy publication, and technical hardening.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  2. Implement DNSSEC to enhance DNS security and prevent spoofing.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear contact information for security incidents, including a security@ or abuse@ email address.
  5. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Plyr
Description
A simple HTML5 media player with custom controls and WebVTT captions.
Key services
HTML5 Video Player, Audio Player, YouTube Player Integration, Vimeo Player Integration, Custom Controls, WebVTT Captions Support
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, SVG, Google Analytics, Google Tag Manager
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • Use of Cloudflare DNS and registrar

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a well-maintained open source media player project site.
  2. No privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails or phone numbers explicitly provided.
  4. Uses modern web technologies and good accessibility practices.
  5. Includes social media links (Twitter) and GitHub repository link.
  6. No forms detected on the main page for data collection.
  7. No security.txt or vulnerability disclosure information found.
  8. No explicit security headers detected in provided data.
  9. Google Analytics and Tag Manager scripts present indicating user tracking.
  10. No suspicious or malicious content detected.
Technical notes

Notes

The website is built with modern, standards-compliant HTML5, CSS3, and JavaScript, including SVG for icons and accessible UI controls. It leverages CDN-hosted assets for fonts and scripts, ensuring fast load times and good performance. Google Analytics and Tag Manager are integrated for analytics and marketing purposes. Hosting and domain registration are managed by Cloudflare, providing reliable infrastructure and DNS services. The site is mobile optimized and accessible, with good SEO metadata including Open Graph and Twitter cards. No CMS or large frameworks are detected, indicating a custom or lightweight implementation. Technical risks include missing DNSSEC and security headers, which could be addressed to improve security posture. Overall, the technical infrastructure is solid and well-maintained.
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. 58/100Medium34 findingsView report
  2. 58/100Medium34 findingsView report
  3. 58/100Medium34 findingsView report
Reviews of this site

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