yalidine.com

We performed a comprehensive analysis of yalidine.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 25940ms. 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 23 KB. 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. Our technology detection scan identified 5 technologies across 4 categories powering yalidine.com. The detected stack includes Bootstrap, reCAPTCHA v3, Cloudflare Turnstile, Cloudflare, and Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, yalidine.com receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, yalidine.com receives a trust score of 63/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, 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, 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 yalidine.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 yalidine.com and identified 5 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. CSS Framework: Bootstrap — provides the styling and responsive layout system for yalidine.com. Security: reCAPTCHA v3 and Cloudflare Turnstile — provides security features like bot detection and CAPTCHA for yalidine.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for yalidine.com. Fonts: Google Fonts — delivers web fonts for typography for yalidine.com.

yalidine.com delivers its homepage in 25940ms (server response time), which is considered slow by industry standards. The total page weight is 23 KB, and we detected 57 resource requests loading assets from 5 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 yalidine.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: 4 out of 8 CSS files and 4 out of 8 JavaScript files are minified. Minifying the remaining 8 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. From an environmental perspective, each page view of yalidine.com produces approximately 0.01g 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 23 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for yalidine.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.

yalidine.com resolves to the IPv4 address 194.163.136.44, 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: arya.ns.cloudflare.com and rommy.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 yalidine.com is handled by yalidine.com with 1 MX records configured: mail.yalidine.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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. 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 yalidine.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 25 active subdomains for yalidine.com: admin.yalidine.com, api.yalidine.com, app.yalidine.com, apps.yalidine.com, blog.yalidine.com, cdn.yalidine.com, community.yalidine.com, and dev.yalidine.com. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of yalidine.com contains 909 words of visible text content. This is a moderate amount of content. The page is structured with 4 H2 headings, 1 H3 headings, 12 H4 headings. The page includes 8 images. 5 images (62%) 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 38% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 28 internal links pointing to other pages on the same domain and 3 external links pointing to third-party websites. There are 8 external JavaScript files, 8 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.

The title tag for yalidine.com is well-optimized at 41 characters: "Le 1er de la livraison express en Algérie". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 41 characters (acceptable): "Le 1er de la livraison express en Algérie". 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://yalidine-express.com.dz/, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to yalidine.com 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 5 terms including Livraison express, Algérie, ecommerce, classique, and COD. 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.