Skip to main content

Security report for teal.fm

Technology · N/a

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

Security score

66/100

Risk levelMedium

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

teal.fm is an early-stage technology startup focused on providing a beautiful and unified music listening tracking and social discovery platform. The website presents a modern, visually appealing interface that highlights key features such as owning your music data, social discovery, universal tracking across platforms, and sharing music taste cards. The business is positioned as a niche service for music enthusiasts and leverages open source principles with community engagement via Discord and Bluesky. Technically, the site uses modern JavaScript modules, React-like SPA architecture, and is hosted with Cloudflare DNS services. Performance and mobile optimization are good, though accessibility and SEO are basic. Security posture is solid with HTTPS and domain transfer protections, but lacks DNSSEC and security headers. Privacy compliance is weak due to missing policies and consent mechanisms. No contact information or formal business credentials are provided, reflecting the pre-launch status. Analytics tracking is implemented via Watson Analytics without disclosed privacy details.

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

8 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 teal.fm

This scan found 20 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
75
Security headers
30
Email security
70
DNS health
85
Network security
100
GDPR outside view
35
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

The company targets music listeners who want to track and share their music history across multiple platforms. Its business model likely revolves around user engagement and data ownership, possibly with future monetization through premium features or community services. The open source approach and social integration suggest a community-driven growth strategy. The startup is small and newly founded in 2024, with no parent or subsidiary companies identified. Partnerships are limited to social platforms and community channels. The market position is nascent, with a focus on differentiation through design and universal tracking capabilities.

Security posture

The website enforces HTTPS and has domain status flags that prevent unauthorized transfers or deletions, indicating good domain management. However, DNSSEC is not enabled, which is a recommended best practice for DNS security. No advanced security headers are detected, and there is no published security or incident response policy. The absence of privacy and cookie policies is a compliance gap, especially under GDPR. Analytics tracking is present but lacks transparency. Overall, the security maturity is moderate, suitable for a startup but requiring improvements before full launch.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Add clear contact information and incident response contacts to improve transparency and user confidence.
  5. Disclose analytics data collection and retention policies to align with privacy best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Track your music listening across all platforms with teal.fm - The most beautiful way to scrobble and analyze your music history. Coming soon.
Key services
music listening data tracking, social music discovery, universal music platform syncing, sharing music taste cards
Content quality
good
Branding
consistent

Technology

Stack
JavaScript ES Modules, Cloudflare DNS, Google Fonts
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • Domain status includes clientTransferProhibited and clientDeleteProhibited

Analytics and tracking

Services
Watson Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
watson.nat.vg
Transparency
poor

Site quality

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

Key observations

  1. Website is a pre-launch music tracking and social discovery platform.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers provided.
  4. Social media presence includes Discord, Bluesky, and GitHub.
  5. Website is modern, visually appealing, and mobile optimized.
  6. Security posture is good but can be improved with DNSSEC and security headers.
  7. Analytics tracking is present but no privacy disclosures.
  8. No forms or data collection fields detected on the landing page.
Technical notes

Notes

The website uses a modern JavaScript module system and likely React framework for a single-page application experience. It leverages Google Fonts for typography and Cloudflare for DNS and possibly CDN services. The site is mobile optimized with responsive design and uses SVG icons for UI elements. Performance is moderate with deferred script loading. No CMS or backend platform is explicitly detected. The technical stack is appropriate for a startup aiming for a clean, modern user experience. Opportunities exist to improve accessibility and SEO by adding ARIA attributes and richer metadata.
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 teal.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 teal.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.