Skip to main content

Security report for nmzrt.hu

Nemzeti Mobilfizetési Zrt. · Government · Hungary

Low risk. 3 critical or high findings in Email security, SSL/TLS and 1 other check.

Security score

79/100

Risk levelLow

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

Nemzeti Mobilfizetési Zrt. operates as a national mobile payment service provider in Hungary, likely affiliated with government services. The website serves as an informational and service portal primarily targeting Hungarian users and businesses involved in mobile payments and electronic toll collection. The business model centers on providing secure and efficient mobile payment solutions at a national scale. The website's market position is strong within Hungary as a trusted government-related entity offering essential payment services. Technically, the website employs modern web technologies including Google Fonts, Google Analytics, Google Tag Manager, and Cookiebot for cookie consent management. The presence of CSRF tokens and security headers indicates a reasonable security posture. The site is mobile-optimized and demonstrates good performance and accessibility basics, although some areas like privacy policy and terms of service documentation are missing or not easily discoverable. From a security perspective, the site uses HTTPS with good SSL configuration and implements standard security headers. Cookie consent is actively managed, supporting GDPR compliance. However, explicit privacy policies, security policies, and incident response information are absent, which could be improved to enhance transparency and compliance. No vulnerabilities or suspicious activities were detected in the analyzed content. Overall, the website is professional, trustworthy, and serves its business purpose effectively. Strategic recommendations include publishing comprehensive privacy and terms of service documents, adding a security policy and incident response contact, and implementing a security.txt file for vulnerability disclosure. These steps would improve compliance, user trust, and security posture.

Scanned

NIS2 and GDPR posture

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

    • High

      No DMARC record found

      DMARC provides email authentication and reporting

      What to do: Add DMARC record: "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

  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
  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 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 nmzrt.hu

This scan found 16 issues across 5 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
67
Security headers
60
Email security
62
DNS health
85
Network security
100
GDPR outside view
100
Average
79

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 nmzrt.hu, from OffSeq Breach.

Total records
10
Employees
0
Customers
0
Third parties
10
Weak passwords
0%

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for nmzrt.hu.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

Nemzeti Mobilfizetési Zrt. holds a key position in Hungary's mobile payment ecosystem, likely operating under government mandate or partnership. Its competitive advantage lies in national coverage and integration with public services such as toll collection. The business model is service-oriented, focusing on payment processing and mobile financial transactions. Revenue streams likely include transaction fees and service contracts with public and private entities. The target customer segments include individual consumers, transport companies, and government agencies. Growth indicators are not explicitly visible but inferred from the national scope and technology adoption. The partnership ecosystem includes Google services for analytics and cookie management, but no direct partner domains were identified. The company's operations appear stable and aligned with national digital payment initiatives.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced with strong SSL configuration, and multiple security headers are present to mitigate common web vulnerabilities. The presence of CSRF tokens and cookie consent mechanisms indicates attention to security and privacy best practices. However, the absence of a published security policy, incident response plan, and vulnerability disclosure mechanism limits transparency and preparedness. Compliance with GDPR is partially indicated by cookie consent but lacks full documentation. No exposed sensitive data or vulnerable libraries were detected. The security culture appears adequate but could benefit from formalized policies and public disclosures to enhance trust and readiness.

Recommendations

  1. Publish a comprehensive privacy policy page clearly accessible from the homepage.
  2. Add terms of service documentation to clarify user and service provider obligations.
  3. Develop and publish a security policy including incident response procedures and contact information.
  4. Implement a security.txt file to facilitate responsible vulnerability disclosure.
  5. Enhance accessibility features to meet higher standards and improve user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Nemzeti Mobilfizetési Zrt.
Description
Egyedi oldalak
Key services
Mobile payment solutions, Electronic toll collection, Payment processing
Content quality
basic
Branding
consistent

Technology

Stack
Google Fonts, Google Tag Manager, Google Analytics, Cookiebot, SweetAlert2
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • CSRF token present
  • Cookie consent implemented

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
Cookiebot
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Cookie consent mechanism is implemented and active.
  3. No explicit privacy policy or terms of service found on the homepage or in metadata.
  4. No contact emails, phone numbers, or physical addresses explicitly found in the provided HTML content.
  5. Use of modern web technologies and Google services for analytics and fonts.
  6. Security headers and HTTPS are properly configured.
  7. Content is primarily in Hungarian language with English alternate link available.
  8. Website branding is consistent with the company name and logo.
  9. No suspicious or malicious indicators detected.
Technical notes

Notes

The website uses a modern technology stack including Google Fonts for typography, Google Analytics and Tag Manager for tracking and analytics, and Cookiebot for cookie consent management. The CSS and JavaScript assets suggest a contemporary frontend framework, possibly Laravel or similar PHP backend. Performance is moderate with fixed background images and responsive design elements. SEO is basic with proper meta tags and Open Graph data but lacks structured data like JSON-LD. Accessibility is basic with some ARIA roles but could be improved. Hosting provider details are not explicit. Overall, the technical infrastructure supports the business needs but has room for modernization and optimization.
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 nmzrt.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 nmzrt.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.