eat24hours.com

HTTP/1.1 Crawled in 31,543ms · June 27, 2026 18:07 UTC

eat24hours.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of eat24hours.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 263ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 3 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, eat24hours.com receives an overall trust score of 53/100, classified as "Caution Advised".
53
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time263ms
ProtocolHTTP/1.1
Page Size3 KB
CompressionNone
Compression SavingsN/A
CDNYes ✓
ServerVarnish
Total Requests8
3rd Party Domains2
RedirectNone
Detected Technologies (0)
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Not set
X-Frame-Options
Not set
X-Content-Type-Options
Not set
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerGlobalSign nv-sa
Issuer FullcountryName=BE, organizationName=GlobalSign nv-sa, commonName=GlobalSign Atlas R3 DV TLS CA 2025 Q4
SubjectcommonName=*.eat24hours.com
Type
TLS VersionTLS 1.2
Cipher SuiteECDHE-RSA-CHACHA20-POLY1305
Algorithm
Issued
Expires— (? days)
SANs

eat24hours.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, eat24hours.com receives a trust score of 53/100, which places it in the "Caution Advised" 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: SPF (Sender Policy Framework) email authentication preventing email spoofing and DMARC email authentication with a reject policy — the strongest available setting. 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, 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 eat24hours.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.
53
/ 100
Caution Advised
Trust Signals
SPF configured
DMARC configured (p=reject)
⚠️ DNSSEC not enabled
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

eat24hours.com Technology Stack & Detected Technologies

🤖 AI Summary
Our automated technology detection scan was unable to identify specific technologies on eat24hours.com. This could indicate that the site uses server-side rendering without client-side technology fingerprints, employs aggressive code obfuscation, or uses custom-built solutions that don't match known technology signatures.

eat24hours.com Performance, Speed & Core Web Vitals

🤖 AI Summary
eat24hours.com delivers its homepage in 263ms (server response time), which is considered fast by industry standards. The total page weight is 3 KB, and we detected 8 resource requests loading assets from 2 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. No compression is currently enabled on eat24hours.com. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 1 CSS files and 0 out of 0 JavaScript files are minified. Minifying the remaining 1 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 eat24hours.com produces approximately 0.0g 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 3 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for eat24hours.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.0g
RatingA
Page Weight & Optimization
HTML Size3 KB
CompressionNone
Compression SavingsN/A
CDNYes ✓
Total Requests8
3rd Party Domains2
CSS Minified0/1
JS Minified0/0

eat24hours.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
eat24hours.com resolves to the IPv4 address 151.101.192.151, 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 4 A record(s) configured. The domain name system is managed by 4 name servers: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, and dns4.p06.nsone.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 eat24hours.com 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for eat24hours.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 24 active subdomains for eat24hours.com: admin.eat24hours.com, api.eat24hours.com, app.eat24hours.com, apps.eat24hours.com, cdn.eat24hours.com, community.eat24hours.com, dev.eat24hours.com, and developers.eat24hours.com. Plus 16 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
151.101.192.151
151.101.64.151
151.101.0.151
151.101.128.151
NS
dns1.p06.nsone.net
dns2.p06.nsone.net
dns3.p06.nsone.net
dns4.p06.nsone.net
MX
aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
aspmx2.googlemail.com
aspmx3.googlemail.com
Email & Authentication
SPF
DMARC p=reject
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (24 found)
admin.eat24hours.com api.eat24hours.com app.eat24hours.com apps.eat24hours.com cdn.eat24hours.com community.eat24hours.com dev.eat24hours.com developers.eat24hours.com docs.eat24hours.com ftp.eat24hours.com help.eat24hours.com m.eat24hours.com mail.eat24hours.com partners.eat24hours.com portal.eat24hours.com shop.eat24hours.com smtp.eat24hours.com staging.eat24hours.com static.eat24hours.com status.eat24hours.com store.eat24hours.com support.eat24hours.com webmail.eat24hours.com www.eat24hours.com

eat24hours.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of eat24hours.com contains 21 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 2 images. 2 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 1 internal link pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 0 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
21
Words
2
Images
0%
Alt Text Score
3
Page Size (KB)
Content Structure
H1Sorry about that
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links1
External Links0
Assets & Features
JavaScript Files0
JS Minified0/0
CSS Files1
CSS Minified0/1
Iframes0
Images2
Missing Alt2
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo

eat24hours.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for eat24hours.com is well-optimized at 54 characters: "Grubhub food delivery is not available in your country". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 186 characters (slightly long): "Free online ordering from restaurants near you! With more than 30,000 restaurants in 500+ cities, food delivery or takeo...". 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://grubhub.com/about/error/out-of-country, preventing duplicate content issues and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Grubhub food delivery is not available in your country..."), OG description, 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.
Google SERP Preview
Grubhub food delivery is not available in your country
https://eat24hours.com
Free online ordering from restaurants near you! With more than 30,000 restaurants in 500+ cities, food delivery or takeout is just a click away. Because with Grubhub: Click, click, food!
Meta Tags
TitleGrubhub food delivery is not available in your country...
Title Length54 chars
Meta Desc Length186 chars
H1Sorry about that
Language
Canonicalhttps://grubhub.com/about/error/out-of-country
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Typewebsite
OG ImageNot set
Twitter Cardsummary_large_image
FaviconSet ✓