Skip to main content

Security report for meetdoc.hu

Healthcare · Hungary

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

Security score

57/100

Risk levelMedium

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

MeetDoc is an online healthcare platform focused on providing patients in Hungary with a simple and fast way to search for doctors and book appointments online without registration. The platform currently lists 175 doctors across major Hungarian cities such as Budapest, Szeged, and Debrecen. The website is built using AngularJS and integrates Google Analytics and Google Tag Manager for tracking user interactions. It also uses Google Maps API to support location-based services. The platform emphasizes ease of use and free access for patients, with a dedicated portal for doctors to manage their presence. Security-wise, the site uses HTTPS and standard tracking tools but lacks visible security headers and formal privacy or cookie policies, which are areas for improvement. No WHOIS data is available for the subdomain hu.meetdoc.com, which is expected as it is a subdomain rather than a separately registered domain. Overall, the site presents a professional and trustworthy healthcare service with moderate technical maturity and some gaps in privacy 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 meetdoc.hu

This scan found 28 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
15
Email security
70
DNS health
60
Network security
100
GDPR outside view
35
Average
57

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

MeetDoc operates in the healthcare sector, targeting patients seeking medical appointments in Hungary. Its business model revolves around providing a free-to-use online appointment booking system that simplifies access to healthcare providers. The platform's moderate size and localized focus suggest a niche market position with potential for growth. The partnership with managedoc.com indicates a broader ecosystem supporting healthcare professionals. Revenue streams are not explicit but may include doctor subscriptions or premium services. The lack of detailed company information and contact data limits transparency but does not detract from the platform's functional value. The use of modern web technologies and integration with Google services supports a scalable and user-friendly experience.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is enforced, ensuring encrypted communication. However, the absence of key security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options reduces protection against common web attacks. No sensitive data exposure or vulnerable libraries were detected in the provided content. The site lacks visible privacy and cookie policies, which is a compliance gap under GDPR. There is no public incident response or security contact information, limiting transparency and readiness for security events. The integration of Google Analytics and Tag Manager is standard but requires proper configuration to ensure privacy compliance. Overall, the security posture is adequate for a healthcare appointment platform but requires enhancements to meet higher compliance and security standards.

Recommendations

  1. Publish comprehensive privacy and cookie policies prominently on the website to improve GDPR compliance.
  2. Implement essential security headers (CSP, X-Content-Type-Options, X-Frame-Options) to enhance protection against web vulnerabilities.
  3. Provide clear contact information including security incident response channels to improve transparency and trust.
  4. Regularly audit and update third-party libraries and scripts to mitigate potential vulnerabilities.
  5. Enhance accessibility features and SEO optimization to improve user experience and reach.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
MeetDoc provides an online doctor search and appointment booking platform, allowing users to find doctors by location, specialty, name, or language spoken. The service offers free usage and instant online appointment booking without registration.
Key services
Doctor search by various criteria, Online appointment booking without registration, Free usage for patients
Content quality
good
Branding
consistent

Technology

Stack
AngularJS, Google Analytics, Google Tag Manager, Google Maps API, jQuery (likely via vendor.min.js), CSS3, HTML5
Frameworks
AngularJS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No visible exposed sensitive data
  • Use of Google Tag Manager for controlled script loading

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a healthcare appointment booking platform targeting Hungarian users.
  2. No WHOIS data for the subdomain, which is expected.
  3. No privacy, cookie, or terms of service policies found on the analyzed page.
  4. No contact emails or phone numbers explicitly provided on the page.
  5. Uses Google Analytics and Google Tag Manager for tracking.
  6. No security headers detected in the provided data.
  7. No visible security or incident response contact information.
  8. Content is professional and relevant to healthcare services.
  9. No adult or questionable content detected.
  10. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website is built on AngularJS, a mature but aging JavaScript framework, which may pose modernization challenges. It uses standard web technologies including CSS3 and HTML5, and integrates Google services for analytics and maps. The site is mobile responsive with good navigation and design quality. Performance is moderate, likely influenced by external scripts and the AngularJS framework. No CMS or hosting provider information was detected. The absence of advanced SEO and accessibility features suggests room for technical improvement. The lack of security headers and privacy compliance mechanisms indicates technical debt in security and compliance domains. Overall, the technical infrastructure supports the business needs but would benefit from modernization and enhanced security controls.
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 meetdoc.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 meetdoc.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.