Skip to main content

Security report for mego.lv

Mego · Other · Latvia

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

Security score

69/100

Risk levelMedium

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

Mego is a Latvian website with a focus on providing services or products under the brand name 'Mego'. The website is built on WordPress and uses modern SEO and cookie consent tools such as Yoast SEO and Cookiebot, indicating a moderate level of digital maturity. The site targets Latvian-speaking users and appears to be relatively new, with content published from mid-2024. The business model and detailed services are not explicitly described in the visible content, limiting full business insight. Technically, the site uses standard web technologies including jQuery, Google Tag Manager, Meta Pixel, and Google Maps API, supporting marketing and analytics efforts. The website is mobile optimized and has good SEO practices but lacks some accessibility features and explicit privacy and contact information.

Scanned

This is an earlier scan of mego.lv. View the latest report

NIS2 and GDPR posture

GDPR outside view
88/ 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

3 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 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching mego.lv

This scan found 17 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. The full timeline opens with your unlock code.

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
52
Security headers
65
Email security
85
DNS health
85
Network security
40
GDPR outside view
88
Average
69

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention mego.lv, from OffSeq Breach.

No leaked records found

Breach holds no records for mego.lv right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The website positions itself as a small Latvian business with a digital presence optimized for local users. It leverages third-party marketing and analytics platforms to enhance user engagement and advertising effectiveness. The absence of detailed business descriptions, contact details, or certifications suggests a focus on digital presence rather than extensive corporate transparency. The use of Cookiebot for GDPR compliance and multiple language alternates indicates awareness of privacy regulations and internationalization. The business likely targets local consumers or clients in Latvia, but further details on market positioning or revenue streams are not available from the content.

Security posture

The website enforces HTTPS and uses a cookie consent mechanism, which are positive security practices. However, no explicit security headers such as Content-Security-Policy or X-Frame-Options were detected, which could improve protection against common web attacks. The lack of visible contact information for security incidents or a security.txt file limits incident response readiness. The use of third-party scripts from trusted domains is standard but requires ongoing monitoring for vulnerabilities. Overall, the security posture is moderate but could be enhanced with additional headers, explicit policies, and incident response contacts.

Recommendations

  1. Implement and publish a comprehensive privacy policy page detailing GDPR compliance and data handling practices.
  2. Add clear contact information including company emails and phone numbers to improve business credibility and user trust.
  3. Configure and deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish a security.txt file to facilitate vulnerability disclosure and improve incident response transparency.
  5. Regularly audit and update third-party scripts and plugins to mitigate potential security vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mego
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Yoast SEO, Cookiebot, Google Tag Manager, Meta Pixel, jQuery, Google Maps API
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Meta Platforms, Inc., Google DoubleClick
Tracking pixels
Meta Pixel
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website uses WordPress CMS with Yoast SEO plugin for optimization.
  2. Cookiebot is implemented for cookie consent management, indicating GDPR awareness.
  3. No explicit privacy policy or terms of service pages found in the HTML content.
  4. No contact emails, phone numbers, or physical addresses found in the visible content.
  5. Multiple external scripts loaded from trusted domains (Google, Facebook, Cookiebot).
  6. Meta Pixel and Google Analytics used for marketing and analytics tracking.
  7. No security.txt or vulnerability disclosure information found.
  8. No explicit security headers detected in the provided data.
  9. Website content is in Latvian language targeting Latvian audience.
  10. Website favicon and logo images are present and consistent with branding.
Technical notes

Notes

The website is built on WordPress CMS with Yoast SEO for search optimization and Cookiebot for cookie management, indicating a modern and compliant technical stack. It uses jQuery and integrates Google Tag Manager and Meta Pixel for analytics and marketing. The site loads Google Maps API for location services. Performance is moderate with good mobile optimization. Accessibility is basic and could be improved. The site uses canonical URLs and hreflang tags for SEO and internationalization. No hosting provider details were found. The site lacks advanced security headers and explicit privacy or terms pages, which are technical gaps to address.
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. 92/100Low11 findingsView report
  2. 67/100Medium27 findingsView report
Reviews of this site

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

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.