Skip to main content

Security report for mehanoid.pro

Other · N/a

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

Security score

48/100

Risk levelHigh

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

The website mehanoid.pro appears to be a small business or project established in 2018, hosted on Beget and built on WordPress with Materialize CSS framework. The site content is accessible and primarily in Russian, but lacks critical compliance documents such as privacy policy, cookie policy, and terms of service. There is no visible contact information or incident response details, which limits user trust and compliance with regulations like GDPR. Technically, the site uses modern front-end frameworks but lacks security headers and advanced security configurations. The domain registration is consistent and legitimate with no privacy protection, indicating transparency in ownership. Overall, the website shows basic digital maturity but requires significant improvements in privacy, security, and business credibility to enhance trust and compliance.

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

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 mehanoid.pro

This scan found 27 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
72
Security headers
15
Email security
65
DNS health
80
Network security
20
GDPR outside view
35
Average
48

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 business behind mehanoid.pro is not clearly identified from the content or metadata. The domain age and hosting suggest a stable small business or personal project. The absence of contact details and compliance policies limits its credibility and market positioning. The site likely targets Russian-speaking users interested in technology or related services, but the business model and revenue streams are unclear. No partnerships or certifications are evident, indicating a standalone operation with limited external validation.

Security posture

Security posture is minimal with no detected security headers, no HTTPS enforcement details, and no incident response contacts. The lack of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. No vulnerability disclosure or security.txt files are present. The site should implement standard security best practices including HTTPS, security headers, and clear privacy and incident response policies to reduce risk and improve user trust.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms.
  2. Add clear contact information including emails and phone numbers for business and security incident reporting.
  3. Enable DNSSEC and configure security headers such as Content-Security-Policy, X-Frame-Options, and HSTS.
  4. Conduct a security audit to identify and remediate any vulnerabilities or outdated libraries.
  5. Establish a vulnerability disclosure program and publish a security.txt file to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
moderate

Technology

Stack
Materialize CSS, Google Fonts, jQuery (implied by Materialize), WordPress (implied by wp-content paths)
Frameworks
Materialize
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
basic
Professionalism
basic
Trustworthiness
low

Key observations

  1. Website is accessible with no blocking or WAF challenge.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails, phone numbers, or physical addresses explicitly found in the content.
  4. Site uses WordPress CMS with Materialize CSS framework.
  5. No security headers detected in the provided data.
  6. No analytics or tracking scripts detected in the provided HTML snippet.
  7. Content is primarily in Russian language but no explicit metadata for privacy or compliance.
  8. No social media links or business certifications found.
  9. WHOIS data shows domain is registered until 2026 with clientTransferProhibited status.
  10. No vulnerability disclosure or security.txt file found.
Technical notes

Notes

The website uses WordPress CMS with Materialize CSS framework and custom fonts. Hosting is provided by Beget, a common provider for small to medium websites. The site is moderately optimized for mobile devices and has a basic SEO setup. However, no advanced analytics or tracking tools were detected. Performance is moderate with no explicit indicators of slow loading but no optimizations like CDN or caching were identified. Accessibility features are basic and could be improved. The technical stack is modern but lacks security hardening and compliance features.
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 mehanoid.pro. 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 mehanoid.pro.

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.