diggy.menu

We performed a comprehensive analysis of diggy.menu on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 8250ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 117 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-23, which is 84 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 5 technologies across 5 categories powering diggy.menu. The detected stack includes Next.js media, React, Webpack, Google Tag Manager, and Google Fonts. The site uses Next.js as its primary framework (version media). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, diggy.menu receives an overall trust score of 69/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, diggy.menu receives a trust score of 69/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 84 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DNSSEC providing authenticated DNS responses, and a well-established domain registered for over 5.2 years, indicating long-term commitment and legitimacy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked diggy.menu against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers. The domain is registered through GoDaddy.com, LLC based in US, with a registration date of 2021-04-22 and expiration date of 2027-04-22.

Our technology detection engine scanned diggy.menu and identified 5 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version media) — provides the application framework and routing for diggy.menu. UI Library: React — handles the user interface rendering and component management for diggy.menu. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for diggy.menu. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for diggy.menu. Fonts: Google Fonts — delivers web fonts for typography for diggy.menu. We also extracted the following tracking identifiers: Google Tag Manager container GTM-M2QXBJH. These IDs can be used to identify other websites operated by the same organization.

diggy.menu delivers its homepage in 8250ms (server response time), which is considered slow by industry standards. The total page weight is 117 KB, and we detected 76 resource requests loading assets from 9 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 0 out of 4 CSS files and 0 out of 35 JavaScript files are minified. Minifying the remaining 39 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of diggy.menu produces approximately 0.06g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 117 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for diggy.menu. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

diggy.menu resolves to the IPv4 address 216.150.1.1, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: jillian.ns.cloudflare.com and julian.ns.cloudflare.com. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for diggy.menu is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for diggy.menu, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. The domain is registered through GoDaddy.com, LLC (US). It was first registered on 2021-04-22 and is set to expire on 2027-04-22, making it 5.2 years old. Our subdomain enumeration scan discovered 3 active subdomains for diggy.menu: api.diggy.menu, blog.diggy.menu, and www.diggy.menu. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of diggy.menu contains 1,116 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 15 H2 headings, 4 H3 headings, 18 H4 headings. The page includes 12 images. 1 images (8%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 92% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 7 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 35 external JavaScript files, 4 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 5 platforms: Facebook (@tr), Instagram (@diggymenu), Linkedin (@diggymenu), Youtube (@diggymenu), and Tiktok (@diggymenu). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for diggy.menu is well-optimized at 52 characters: "Diggy - Soluções em Cardápio Digital, Delivery e PDV". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 97 characters (well-optimized): "Automatize seu negócio, receba pedidos por WhatsApp com cardápio digital, pdv e muito maisrobots.". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The page language is declared as pt-br and the meta robots directive is set to index,follow. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Diggy - Cardápio Digital e PDV..."), OG description, OG image (social sharing thumbnail), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The meta keywords tag contains 10 terms including Cardápio Digital Online, WhatsApp, Sistema PDV, Delivery, and Gestor de Pedidos. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.