Skip to main content

Security report for speakly.me

Speakly · Education · United States

Medium risk. 6 critical or high findings in Email security, Security headers and 1 other check.

Security score

55/100

Risk levelMedium

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

Speakly is a modern language learning platform offering online courses in multiple languages such as Spanish, French, and German. The website targets a global audience of language learners and positions itself as a fast and effective learning solution with over a million users. The business model is subscription-based, focusing on delivering educational content through a web and mobile app interface. The company was founded in 2016 and maintains a medium-sized presence in the education sector. Technically, the website uses modern JavaScript frameworks like Vue.js and integrates Google Tag Manager for analytics, indicating a moderate level of digital maturity. The site is mobile optimized and provides a good user experience with professional design and clear navigation. Security-wise, the website uses HTTPS and implements cookie consent mechanisms but lacks visible security headers and explicit privacy policies, which are areas for improvement. Overall, the site is legitimate and professionally maintained but would benefit from enhanced transparency and security practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

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

Keep watching speakly.me

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
72
Security headers
15
Email security
40
DNS health
80
Network security
40
GDPR outside view
83
Average
55

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

Speakly operates in the education sector, specifically in language learning. It leverages a subscription-based business model targeting individual learners worldwide. The platform's competitive advantage lies in its promise of accelerated learning and a user base exceeding one million. The company appears to have a consistent branding strategy and a professional online presence. Revenue streams likely include subscription fees and possibly in-app purchases. The absence of explicit contact information and privacy policies suggests room for growth in customer trust and compliance. The partnership ecosystem is not evident from the data, and no related or subsidiary domains were identified. Strategic observations include the need for clearer compliance documentation and enhanced security posture to support growth and user trust.

Security posture

The website demonstrates a basic to moderate security maturity level. HTTPS is enforced, and a cookie consent mechanism is present, indicating awareness of privacy regulations. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces the overall security posture. No exposed sensitive data or vulnerable libraries were detected in the provided content. The absence of a security policy, incident response contacts, or vulnerability disclosure mechanisms indicates gaps in compliance and readiness. These gaps could impact business operations if exploited. The company should prioritize publishing privacy and security policies, enabling DNSSEC, and implementing security headers to enhance protection and compliance with GDPR and other regulations.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service accessible from the website footer.
  2. Implement and configure essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide clear contact information for general inquiries and security incidents, including dedicated security and abuse email addresses.
  4. Enable DNSSEC for the domain to improve DNS security.
  5. Conduct regular security audits of third-party scripts and dependencies to identify and mitigate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Speakly
Description
A modern language learning app used by over a million people worldwide. Learn a new language online: learn Spanish, French, German, and other foreign languages.
Key services
Language learning app, Online language courses
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Vue.js, Google Tag Manager, CookieYes
Frameworks
Vue.js
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Cookie consent mechanism implemented
  • No exposed sensitive data found

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
CookieYes
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No explicit privacy policy or terms of service found in the provided HTML content.
  3. Cookie consent mechanism is implemented via CookieYes.
  4. No direct contact emails or phone numbers found in the HTML content.
  5. Uses modern JavaScript framework Vue.js and Google Tag Manager for analytics.
  6. Domain is privacy protected but has a stable registration history.
  7. No security.txt or vulnerability disclosure page detected.
  8. No explicit security policy or incident response contact information found.
  9. Website content is professionally presented and targeted at language learners.
  10. No suspicious or malicious indicators detected.
Technical notes

Notes

The website is built using Vue.js, a modern JavaScript framework, indicating a contemporary front-end architecture. Google Tag Manager is used for analytics and marketing tracking, and CookieYes manages cookie consent. The domain uses DNS servers from zone.eu and related providers, but DNSSEC is not enabled, which is a minor security gap. The site appears to be hosted on a provider not explicitly identified in the data. Performance is moderate with preloading of scripts and responsive design for mobile devices. Accessibility features are basic, with room for improvement. SEO is supported by proper meta tags and Open Graph data. Overall, the technical infrastructure is solid but could benefit from enhanced security configurations and accessibility improvements.
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 speakly.me. 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 speakly.me.

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.