Skip to main content

Security report for simplepartner.hu

Otp Mobil Kft. · Finance · Hungary

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

Security score

45/100

Risk levelHigh

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

The website simplepartner.hu represents Otp Mobil Kft., a medium-sized Hungarian company founded in 2015, operating in the finance and technology sectors. The business focuses on providing online payment systems, mobile applications, and corporate solutions such as parking and e-vignette services. The site positions itself as a partner for e-commerce merchants and corporate clients requiring flexible payment and mobile financial services. The market position appears stable with links to related domains indicating a broader service ecosystem. Technically, the website is built with basic HTML and CSS without advanced frameworks or CMS detected. The site is moderately optimized for mobile devices and has a simple navigation structure. However, it lacks modern SEO and accessibility features and does not include analytics or tracking technologies. Performance is moderate with no visible technical debt but opportunities exist for modernization and improved user experience. From a security perspective, the site does not display privacy or cookie policies, lacks security headers, and does not provide contact information for incident response. No HTTPS or SSL configuration details were provided, limiting the security posture assessment. The domain WHOIS data is consistent and supports the legitimacy of the business. Overall, the security maturity is basic with room for significant improvements in compliance and protection. The overall risk is moderate due to the absence of critical security issues but the lack of privacy compliance and contact information reduces trust. Strategic recommendations include implementing privacy and cookie policies, enhancing security headers, improving mobile and accessibility features, and providing clear contact and incident response channels to strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  3. 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 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 simplepartner.hu

This scan found 26 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
62
Security headers
40
Email security
70
DNS health
75
Network security
0
GDPR outside view
25
Average
45

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 · found on this site
  • 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

Otp Mobil Kft. operates in the Hungarian financial technology sector, offering payment processing and mobile financial services primarily targeting e-commerce merchants and corporate clients. The company benefits from its association with the OTP Group, a major financial institution in Hungary, which likely provides market credibility and resources. The business model revolves around providing flexible payment solutions and mobile applications that integrate with various service providers. The presence of corporate solutions such as parking and e-vignette services indicates diversification and a focus on B2B services. The website's minimal content suggests a focus on directing users to partner sites for detailed services, indicating a partner-driven ecosystem. Growth potential exists through expanding mobile services and corporate offerings. The lack of direct contact information on the site may limit direct customer engagement but aligns with a partner-centric approach.

Security posture

The current security posture of the website is basic and lacks several best practices. The absence of privacy and cookie policies indicates non-compliance with GDPR and related regulations. No security headers such as Content-Security-Policy or X-Frame-Options are present, increasing risk exposure. The lack of HTTPS information limits confidence in secure communications. No incident response or abuse contact channels are provided, which is a gap in security readiness. No vulnerabilities or exposed sensitive data were detected in the provided content, but the minimal technical implementation suggests limited attack surface. Overall, the site requires enhancements in privacy compliance, security headers, and incident response capabilities to improve its security maturity and reduce risk.

Recommendations

  1. Implement and prominently display a comprehensive privacy policy and cookie policy to ensure GDPR compliance.
  2. Configure and enforce HTTPS with strong SSL/TLS settings to secure all communications.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear contact information including security incident response and abuse reporting channels.
  5. Improve mobile optimization and accessibility to enhance user experience and compliance with accessibility standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Otp Mobil Kft.
Description
The website offers online payment systems, mobile applications, and corporate solutions such as parking and e-vignette services for companies and organizations.
Key services
Online payment system, Mobile application, Corporate solutions (parking, e-vignette, etc.)
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

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 provided.
  4. Content is minimal but relevant to the business services offered.
  5. External links point to related payment and mobile service domains.
  6. No analytics or tracking scripts detected in the HTML content.
  7. No social media links or contact forms present.
  8. Basic mobile menu toggle implemented via JavaScript.
  9. No security headers or advanced security features visible in the HTML.
  10. WHOIS data is consistent and domain age supports business legitimacy.
Technical notes

Notes

The website uses basic HTML and CSS without any detected JavaScript frameworks or CMS platforms. The mobile menu toggle is implemented with a simple inline JavaScript function. No analytics or tracking scripts are present, indicating minimal data collection. The site lacks meta tags beyond viewport and charset, limiting SEO effectiveness. No structured data (JSON-LD or Open Graph) is present. The hosting provider and platform are not identifiable from the content. Performance is likely moderate given the minimal content and simple design. Opportunities exist to modernize the tech stack, improve SEO, and enhance accessibility and mobile responsiveness.
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. 45/100High35 findingsView report
Reviews of this site

Share your experience with simplepartner.hu. 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 simplepartner.hu.

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.