Skip to main content

Security report for omoguru.com

Omoguru · Education · N/a

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

61/100

Risk levelMedium

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

Omoguru is a small education-focused company providing accessible reading and learning applications such as Lexie, w3Lexie plugin, and ReadAble widget. Their market position targets pupils, students, and individuals with reading difficulties, including dyslexia. The website is built on WordPress with modern technologies and includes standard marketing and tracking tools like Google Analytics and Facebook Pixel. Security posture is generally good with HTTPS and cookie consent mechanisms, but lacks some security headers and explicit privacy and terms pages. WHOIS data is missing, which raises some concerns about domain registration legitimacy. Overall, the site is professional and trustworthy 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

4 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching omoguru.com

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. 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
77
Security headers
15
Email security
75
DNS health
75
Network security
40
GDPR outside view
83
Average
61

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

Omoguru operates in the education sector with a SaaS business model offering free and subscription-based tiers. Their competitive advantage lies in accessibility and customization for reading and learning. The company maintains a consistent brand and active social media presence, indicating engagement with their target audience. Partnerships such as with omotype.com suggest a collaborative ecosystem. Revenue streams likely include subscriptions and possibly enterprise or educational licenses. Growth indicators are positive given the modern website and active content updates.

Security posture

The website employs HTTPS and a comprehensive cookie consent mechanism, demonstrating awareness of privacy and security compliance. However, the absence of security headers and a security.txt file indicates room for improvement in defense-in-depth. No exposed sensitive data or vulnerabilities were detected in the content. The lack of explicit privacy policy and terms of service pages is a compliance gap. Incident response readiness and contact channels for security issues are not evident, which could hinder timely response to threats.

Recommendations

  1. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection.
  2. Publish comprehensive privacy policy and terms of service pages to improve compliance and user trust.
  3. Add a security.txt file to facilitate vulnerability disclosure and incident reporting.
  4. Provide clear and verified contact information including security and support emails.
  5. Investigate and resolve the missing WHOIS registration data to ensure domain legitimacy and reduce risk.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Omoguru
Description
Omoguru improves, encourages and facilitates reading and learning. Apps for enjoyable reading, surfing and accessibility.
Key services
Lexie app, w3Lexie browser plugin, ReadAble accessibility widget, Reading lab
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.2, Oxygen Builder, jQuery 3.7.1, FontAwesome 5.15.4, Google Tag Manager, Facebook Pixel, CookieYes cookie consent
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • Cookie consent banner with customization
  • No exposed sensitive data found

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Facebook Ads
Tracking pixels
Facebook Pixel
Marketing tools
CookieYes
Transparency
good

Site quality

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

Key observations

  1. Website is accessible and not blocked by WAF or security mechanisms.
  2. No WHOIS registration data found, which is unusual and warrants caution.
  3. Cookie consent mechanism is implemented with detailed categories and user controls.
  4. No explicit privacy policy or terms of service pages detected in the provided content.
  5. No explicit contact emails or phone numbers found in the visible content.
  6. Social media presence is strong with official accounts linked.
  7. Website uses modern technologies and SEO best practices.
  8. No security headers detected in the provided data; recommend adding.
  9. No vulnerability disclosure or security.txt found.
  10. Content is safe and suitable for general audiences.
Technical notes

Notes

The website is built on WordPress 6.8.2 using Oxygen Builder, with jQuery and FontAwesome for UI elements. It integrates Google Tag Manager and Facebook Pixel for analytics and marketing. CookieYes is used for cookie consent management. The site appears mobile optimized and SEO friendly with proper meta tags and structured data. Performance is moderate, with potential improvements in hosting and caching. No critical technical debt or outdated libraries were detected. The absence of security headers is a technical risk that should be addressed.
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 omoguru.com. 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 omoguru.com.

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.