Skip to main content

Security report for zomato.com

Zomato™ Ltd. · E-commerce · India

Low risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

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

Zomato™ Ltd. operates India’s largest food delivery, dining, and restaurant discovery platform, positioning itself as the market leader in the Indian food tech space. The company offers a comprehensive suite of services including online food ordering, restaurant discovery, and partnerships with restaurants and delivery personnel. Its digital presence is supported by a modern, mobile-optimized website built on the Astro framework, complemented by dedicated mobile applications for Android and iOS. The website demonstrates excellent content quality, clear navigation, and strong branding consistency, targeting general consumers across India. From a technical perspective, Zomato employs a contemporary tech stack with client-side hydration and performance optimizations, ensuring fast load times and a seamless user experience on both desktop and mobile devices. Security best practices are evident with enforced HTTPS, presence of key security headers, and a dedicated security policy page. However, the absence of explicit incident response contacts and vulnerability disclosure mechanisms suggests room for improvement in transparency and security communication. The WHOIS data for the domain www.zomato.com is notably absent, which is unusual for a large enterprise and may indicate privacy protection or technical issues with the registrar. Despite this, the website’s extensive branding, linked subsidiaries, and external references strongly support its legitimacy. No adult or explicit content is present, making the site safe for general audiences. Overall, Zomato exhibits a mature digital infrastructure with a strong security posture and comprehensive privacy compliance, though it could enhance its incident response and vulnerability disclosure transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

4 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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching zomato.com

This scan found 18 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. See sample alerts.

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
100
Security headers
35
Email security
80
DNS health
85
Network security
100
GDPR outside view
53
Average
76

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

Total records
38,287
Employees
7
Customers
36,869
Third parties
1,411
Weak passwords
20%

Latest record dated 2026-06-08 · 26 subdomains affected

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

Select it in the checkout above.

Masked preview

  • –www.zomato.com2026-06-08
  • –www.zomato.com2026-05-14
  • –zomato.com2025-11-05
  • –zomato.com2025-09-12
  • –www.zomato.com2025-08-20

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

Zomato holds a dominant position in the Indian food delivery and restaurant discovery market, leveraging a large network of over 300,000 restaurants across 800+ cities and billions of orders delivered. Its business model revolves around connecting consumers with restaurants via online ordering and delivery services, supplemented by value-added offerings such as party planning, gift cards, and gourmet options. The company’s ecosystem includes subsidiaries like Blinkit, District, and Hyperpure, expanding its reach into grocery delivery, events, and supply chain solutions. Zomato’s revenue streams likely include commissions from restaurant partners, delivery fees, advertising, and subscription programs such as Zomato Gold. The company targets a broad consumer base in India, emphasizing convenience, variety, and savings. Strategic partnerships and a robust app presence underpin its competitive advantage and growth trajectory.

Security posture

Zomato demonstrates a strong security posture with HTTPS enforced site-wide, comprehensive security headers, and a dedicated security policy page. The site avoids exposing sensitive data in its HTML and uses modern JavaScript frameworks without known vulnerable libraries. However, the absence of explicit incident response contact information and a vulnerability disclosure program limits transparency and may delay response to security incidents. Privacy compliance is robust, with clear privacy and cookie policies and consent mechanisms in place, aligning with GDPR principles. The site’s moderate user tracking via Datadog RUM is balanced with privacy considerations. Overall, Zomato’s security maturity is high but could benefit from enhanced incident response readiness and public vulnerability disclosure.

Recommendations

  1. Publish explicit incident response contact details and abuse reporting channels to improve security transparency.
  2. Implement and publicize a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  3. Regularly audit and update third-party libraries and scripts to mitigate potential vulnerabilities.
  4. Enhance user privacy controls and provide clearer data retention policies to strengthen GDPR compliance.
  5. Maintain and communicate security certifications or compliance frameworks to bolster trust and credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Zomato™ Ltd.
Description
India’s largest Food Delivery, Dining and Restaurant Discovery Service. Better food for more people.
Key services
Food delivery, Dining, Restaurant discovery, Online ordering, Partnering with restaurants and delivery partners
Content quality
excellent
Branding
consistent

Technology

Stack
Astro, JavaScript, CSS, HTML
Frameworks
Astro v5.3.0
Platforms
Web, Mobile apps (Android, iOS)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Security policy page available
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected in scripts

Analytics and tracking

Services
Datadog RUM
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
DatadogRUM
Marketing tools
Datadog
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and professional design.
  2. Strong brand presence with multiple subsidiary and partner domains linked.
  3. Comprehensive privacy, security, and terms of service policies are available.
  4. No direct contact emails or phone numbers found in HTML; contact via forms and support pages.
  5. No WHOIS data available, which is unusual for a large enterprise domain.
  6. No signs of adult or explicit content; content is safe for general audiences.
  7. Modern tech stack with Astro framework and client-side hydration.
  8. Mobile optimized with app download links prominently displayed.
  9. Security headers and HTTPS enforced indicating good security posture.
  10. No explicit incident response or vulnerability disclosure pages found.
Technical notes

Notes

The website is built using the Astro framework (v5.3.0), leveraging modern JavaScript and CSS for a responsive and performant user experience. Client-side hydration techniques are used for dynamic content rendering. The site is optimized for mobile devices with dedicated app download links and preloaded assets. SEO best practices are followed with proper meta tags and Open Graph data. No CMS or hosting provider details are explicitly detected. Performance is fast with minimal blocking scripts. Accessibility features are present but could be further enhanced. The technical infrastructure supports a scalable and secure platform suitable for a large enterprise food delivery service.
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 zomato.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 zomato.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.