allofresh.id

We performed a comprehensive analysis of allofresh.id on 2026-07-06. The website returned an HTTP 200 status code with a server response time of 7134ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 707 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 Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-09-08, which is 64 days from now. The security headers analysis reveals a score of 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing 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 12 technologies across 10 categories powering allofresh.id. The detected stack includes Magento, Next.js, React, Vue.js, Bootstrap, Webpack, Vite, Google Tag Manager, LiveChat, Google Fonts, YouTube Embed, and jQuery. The primary e-commerce platform is Magento. The site uses Next.js as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, allofresh.id receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, allofresh.id receives a trust score of 80/100, which places it in the "Very 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 Google Trust Services with 64 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. Areas of concern include: 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 allofresh.id 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 allofresh.id and identified 12 distinct technologies across 10 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Ecommerce: Magento — powers the online store and shopping functionality for allofresh.id. Framework: Next.js — provides the application framework and routing for allofresh.id. UI Library: React and Vue.js — handles the user interface rendering and component management for allofresh.id. CSS Framework: Bootstrap — provides the styling and responsive layout system for allofresh.id. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for allofresh.id. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for allofresh.id. Chat: LiveChat — provides live chat and customer communication for allofresh.id. Fonts: Google Fonts — delivers web fonts for typography for allofresh.id. Video: YouTube Embed — provides video hosting and playback for allofresh.id. JavaScript Library: jQuery — provides utility functions and DOM manipulation for allofresh.id. We also extracted the following tracking identifiers: Google Tag Manager container GTM-526LW3M. These IDs can be used to identify other websites operated by the same organization.

allofresh.id delivers its homepage in 7134ms (server response time), which is considered slow by industry standards. The total page weight is 707 KB, and we detected 16 resource requests loading assets from 3 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 2 CSS files and 1 out of 2 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 allofresh.id produces approximately 0.35g 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 707 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for allofresh.id. 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.

allofresh.id resolves to the IPv4 address 172.66.157.223 and also supports IPv6 (2606:4700:10::6814:1a83), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: imani.ns.cloudflare.com and margo.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 allofresh.id is handled by Google Workspace with 4 MX records configured: alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, and alt3.aspmx.l.google.com and 1 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 allofresh.id. 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.

The homepage of allofresh.id contains 650 words of visible text content. This is a moderate amount of content. The page is structured with 8 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 7 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 1 internal link pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 2 external JavaScript files, 2 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on allofresh.id: JCB and Google Pay. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 1 platforms: Github (@zloirock). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for allofresh.id is well-optimized at 60 characters: "Allofresh: Belanja Online Kebutuhan Rumah Tangga Murah Lebay". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 156 characters (acceptable): "Belanja online kebutuhan bulanan rumah tangga kini lebih mudah dan cepat. Beli produk segar hingga sembako berkualitas, ...". 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 en, the meta robots directive is set to index,follow, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to allofresh.id on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The meta keywords tag contains 6 terms including transmart online, allofresh, groceries, quick commerce, and belanja bulanan. 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.