Skip to main content

Security report for meetdoc.com

Healthcare · Hungary

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

58/100

Risk levelMedium

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

MeetDoc is a Hungarian healthcare-focused online platform that facilitates doctor search and appointment booking primarily in major Hungarian cities. The platform offers free and instant online appointment scheduling without requiring user registration, targeting patients seeking convenient access to medical professionals. The website is modest in size and scope, with a database of approximately 175 doctors, positioning itself as a niche regional service provider in the healthcare sector. Technically, the website is built using AngularJS, an older JavaScript framework, and integrates Google Analytics and Google Tag Manager for user tracking and analytics. The site loads with moderate performance and basic mobile optimization. However, it lacks modern security headers and advanced SEO or accessibility features. The absence of privacy and cookie policies, as well as contact information, indicates gaps in compliance and user trust facilitation. From a security perspective, the website uses HTTPS and has a domain with a long registration history and locked transfer status, which supports legitimacy. Nonetheless, the lack of DNSSEC, security headers, and vulnerability disclosure mechanisms suggests room for improvement in security posture. No critical vulnerabilities or adult content were detected, and the site is safe for general audiences. Overall, MeetDoc presents a functional but basic healthcare service platform with moderate technical maturity and security posture. Strategic improvements in privacy compliance, security best practices, and user trust signals would enhance its credibility and resilience in the digital healthcare market.

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

8 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.com

This scan found 29 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
65
Network security
100
GDPR outside view
35
Average
58

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 meetdoc.com, from OffSeq Breach.

Total records
12
Employees
0
Customers
0
Third parties
12
Weak passwords
83%

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 meetdoc.com.

Select it in the checkout above.

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

Open in Breach(opens in a new tab)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

MeetDoc operates in the healthcare sector, focusing on providing an online platform for patients to find doctors and book appointments in Hungary. Its competitive advantage lies in offering free, instant online booking without registration, simplifying patient access to healthcare providers. The business model revolves around connecting patients with doctors, potentially monetizing through partnerships or premium services for medical professionals. The platform targets patients in urban Hungarian areas, with a relatively small but focused database of doctors. The company appears to maintain partnerships, as indicated by the link to managedoc.com, which may serve doctors or related healthcare services. The website's longevity since 2004 suggests stable operations, though the technical stack indicates some legacy components. Growth opportunities may include expanding doctor listings, geographic coverage, and enhancing digital marketing and compliance to build trust and user base. Revenue streams are not explicit but may include service fees from doctors or advertising. The platform's ecosystem is limited but could benefit from strategic alliances and improved digital presence.

Security posture

The security maturity of MeetDoc is moderate. The website enforces HTTPS, which is mandatory for secure communications. The domain is registered with a reputable registrar, NETIM SAS, since 2004, with clientTransferProhibited status, reducing risk of hijacking. However, DNSSEC is not enabled, which could expose DNS spoofing risks. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which are important for mitigating common web attacks. No privacy or cookie policies were found, indicating potential GDPR compliance gaps. The absence of a vulnerability disclosure policy or security.txt file suggests limited incident response readiness. The use of Google Analytics and Tag Manager without visible consent mechanisms raises privacy concerns. No exposed sensitive data or vulnerable libraries were identified in the provided content. Recommendations include implementing DNSSEC, adding security headers, publishing privacy and cookie policies, and establishing a vulnerability disclosure process to improve security posture and compliance.

Recommendations

  1. Implement DNSSEC to enhance domain name system security.
  2. Add essential security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Introduce a cookie consent mechanism to comply with privacy regulations.
  5. Establish a vulnerability disclosure policy or security.txt file to facilitate incident reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
MeetDoc is an online doctor search and appointment booking platform primarily serving Hungarian cities such as Budapest, Szeged, and Debrecen. It offers a free appointment booking system with instant online booking without registration.
Key services
Doctor search by location, specialty, name, language, Online appointment booking without registration
Content quality
basic
Branding
moderate

Technology

Stack
AngularJS, Google Analytics, Google Tag Manager, Google Maps API
Frameworks
AngularJS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited domain status

Analytics and tracking

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

Advertising

Transparency
basic

Site quality

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

Key observations

  1. No privacy, cookie, or terms of service policies found on the site.
  2. No contact emails or phone numbers explicitly provided on the main page.
  3. The site uses AngularJS, which is an older framework, indicating potential technical debt.
  4. Google Analytics and Google Tag Manager are used for tracking, but no cookie consent mechanism is present.
  5. The site is focused on Hungarian healthcare appointment booking with limited geographic scope.
  6. No security headers detected in the HTML content; SSL is enabled but no advanced security configurations observed.
  7. External link to managedoc.com suggests a partner or related service for doctors.
  8. No social media links or company contact details found in the provided content.
  9. The site content is in Hungarian language with some English elements (e.g., 'Search' button).
Technical notes

Notes

The website uses AngularJS, an older JavaScript framework, which may pose maintainability and security challenges. It integrates Google Analytics and Google Tag Manager for analytics and tracking. The site loads external scripts from Google domains and Google Maps API, indicating some reliance on third-party services. The HTML structure is valid but minimal in metadata, lacking Open Graph or JSON-LD structured data. Performance is moderate with basic mobile optimization and accessibility features. SEO optimization is basic, with minimal meta descriptions and no structured data. The site does not appear to use a CMS or modern frontend frameworks beyond AngularJS. Hosting provider details are not disclosed. There is potential technical debt due to legacy frameworks and missing modern web standards implementation.
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.com. 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.com.

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.