tabelog.com

We performed a comprehensive analysis of tabelog.com on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 9254ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 533 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 DigiCert Inc (OV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-11-28, which is 152 days from now. The security headers analysis reveals a score of 45/100 (below average). The following security headers are properly configured: X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 4 technologies across 4 categories powering tabelog.com. The detected stack includes React, Google Tag Manager, Google Ads, and jQuery 3.4.1.. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, tabelog.com receives an overall trust score of 73/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, tabelog.com receives a trust score of 73/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, a valid SSL certificate issued by DigiCert Inc with 152 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked tabelog.com 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.

Our technology detection engine scanned tabelog.com and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for tabelog.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for tabelog.com. Advertising: Google Ads — handles advertising pixel tracking and conversion measurement for tabelog.com. JavaScript Library: jQuery (version 3.4.1.) — provides utility functions and DOM manipulation for tabelog.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-KVVB8K2. These IDs can be used to identify other websites operated by the same organization.

tabelog.com delivers its homepage in 9254ms (server response time), which is considered slow by industry standards. The total page weight is 533 KB, and we detected 1432 resource requests loading assets from 11 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: 2 out of 9 CSS files and 1 out of 12 JavaScript files are minified. Minifying the remaining 18 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 tabelog.com produces approximately 0.26g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 533 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for tabelog.com. 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.

tabelog.com resolves to the IPv4 address 172.66.1.98, 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 2 A record(s) configured. The domain name system is managed by 4 name servers: ns-1261.awsdns-29.org, ns-1879.awsdns-42.co.uk, ns-34.awsdns-04.com, and ns-629.awsdns-14.net. Having 4 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 tabelog.com is handled by Google Workspace with 1 MX records configured: smtp.google.com. 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for tabelog.com. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions. Our subdomain enumeration scan discovered 6 active subdomains for tabelog.com: admin.tabelog.com, api.tabelog.com, help.tabelog.com, mail.tabelog.com, support.tabelog.com, and www.tabelog.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of tabelog.com contains 2,393 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 21 H2 headings, 11 H3 headings, 0 H4 headings. The page includes 154 images. 3 images (2%) 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 98% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 1,210 internal links pointing to other pages on the same domain and 40 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 12 external JavaScript files, 9 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and Schema.org structured data (WebSite). Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for tabelog.com is good at 29 characters: "食べログ【掲載店舗数No.1】グルメ・レストラン予約サイト". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 119 characters (well-optimized): "お店探し・ネット予約ならグルメサイト「食べログ」で！全国にあるレストラン901,869件の飲食店情報を掲載中。独自のランキングやユーザーの口コミ・写真をもとに、様々なジャンルの人気のレストラン、目的や予算にぴったりのお店が見つけられます！". 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 canonical url is correctly set to https://tabelog.com/, preventing duplicate content issues, the page language is declared as ja, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("グルメ・レストランガイド..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.