ooredoo.dz

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, ooredoo.dz receives a trust score of 66/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 quarantine 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, 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 ooredoo.dz 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.

🤖 AI Summary

Our technology detection engine scanned ooredoo.dz and identified 9 distinct technologies across 8 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 ooredoo.dz. CSS Framework: Tailwind CSS — provides the styling and responsive layout system for ooredoo.dz. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for ooredoo.dz. Analytics: Microsoft Clarity — tracks visitor behavior and provides traffic insights for ooredoo.dz. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for ooredoo.dz. Advertising: Meta Pixel and Snapchat Pixel — handles advertising pixel tracking and conversion measurement for ooredoo.dz. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for ooredoo.dz. JavaScript Library: jQuery — provides utility functions and DOM manipulation for ooredoo.dz. We also extracted the following tracking identifiers: Google Tag Manager container GTM-54KVSJHB and Meta (Facebook) Pixel ID 543383735871123. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

ooredoo.dz delivers its homepage in 31028ms (server response time), which is considered slow by industry standards. The total page weight is 833 KB, and we detected 519 resource requests loading assets from 20 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 11 CSS files and 2 out of 12 JavaScript files are minified. Minifying the remaining 19 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 ooredoo.dz produces approximately 0.41g of CO₂, earning a carbon rating of D. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 833 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ooredoo.dz. 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.

🤖 AI Summary

ooredoo.dz resolves to the IPv4 address 80.88.14.227, 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: ns1.ooredoo.dz and ns2.ooredoo.dz. 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 ooredoo.dz is handled by ooredoo.dz with 2 MX records configured: mail1.ooredoo.dz and mail2.ooredoo.dz. 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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 ooredoo.dz. 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 9 active subdomains for ooredoo.dz: api.ooredoo.dz, apps.ooredoo.dz, m.ooredoo.dz, partners.ooredoo.dz, static.ooredoo.dz, store.ooredoo.dz, support.ooredoo.dz, and webmail.ooredoo.dz. Plus 1 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of ooredoo.dz contains 1,510 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 22 H2 headings, 34 H3 headings, 1 H4 headings, 6 H5, and 0 H6 headings. The page includes 158 images. 32 images (20%) 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 80% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 269 internal links pointing to other pages on the same domain and 47 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, 11 CSS stylesheets, and 1 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 website has social media presence across 5 platforms: Facebook (@tr), Twitter (@ooredoodz), Instagram (@ooredooalgerie), Linkedin (@ooredoo-algerie), and Tiktok (@ooredooalgerie). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for ooredoo.dz is too long at 71 characters: "Ooredoo Algérie - Offres Mobile, Internet et Services - Ooredoo Algeria". At 71 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 157 characters (acceptable): "Ooredoo vous propose les meilleurs offres Mobile, Internet et Service pour les particuliers et entreprises. Découvrez no...". 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://www.ooredoo.dz/fr/, preventing duplicate content issues, the page language is declared as fr-fr, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Ooredoo Algérie - Offres Mobile, Internet et Services - Oore..."), 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. The meta keywords tag contains 20 terms including offres internet algerie, offres mobile algérie, ooredoo algérie, offres mobilis internet, and meilleur offre mobile algerie. 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.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with ooredoo.dz. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: gtm_id: GTM-54KVSJHB, meta_pixel_id: 543383735871123.

🤖 AI Summary

This section shows additional intelligence about ooredoo.dz including data breach history (via HaveIBeenPwned), web archive history (Wayback Machine), green/eco-friendly hosting status, and mobile app presence in the iOS App Store.