ejabiah.com

We performed a comprehensive analysis of ejabiah.com on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 38293ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 60 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Starfield Technologies, Inc. (DV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES256-GCM-SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2027-02-16, which is 229 days from now. 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 7 technologies across 7 categories powering ejabiah.com. The detected stack includes Bootstrap, Google Analytics 4, Google Tag Manager, Meta Pixel, Cloudflare, jQuery 3.6.0., and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ejabiah.com receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, ejabiah.com receives a trust score of 68/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 Starfield Technologies, Inc. with 229 days until expiration, 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 ejabiah.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 ejabiah.com and identified 7 distinct technologies across 7 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 ejabiah.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for ejabiah.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for ejabiah.com. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for ejabiah.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for ejabiah.com. JavaScript Library: jQuery (version 3.6.0.) — provides utility functions and DOM manipulation for ejabiah.com. Icon Set: Font Awesome — provides additional functionality for ejabiah.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-L2Q4861LMQ, Google Tag Manager container GTM-TSDNH9BJ, and Meta (Facebook) Pixel ID 1762406034590332. These IDs can be used to identify other websites operated by the same organization.

ejabiah.com delivers its homepage in 38293ms (server response time), which is considered slow by industry standards. The total page weight is 60 KB, and we detected 145 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: 6 out of 20 CSS files and 15 out of 22 JavaScript files are minified. Minifying the remaining 21 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 ejabiah.com produces approximately 0.03g 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 60 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ejabiah.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.

ejabiah.com resolves to the IPv4 address 107.180.34.104, 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 5 name servers: ns10.sahara.com.sa, ns11.sahara.com.sa, ns14.sahara.com.sa, ns69.domaincontrol.com, and ns70.domaincontrol.com. Having 5 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 ejabiah.com is handled by Microsoft 365 with 1 MX records configured: ejabiah-com.mail.protection.outlook.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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for ejabiah.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.

The homepage of ejabiah.com contains 271 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 7 H2 headings, 11 H3 headings, 6 H4 headings, 3 H5, and 0 H6 headings. The page includes 29 images. 3 images (10%) 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 90% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 43 internal links pointing to other pages on the same domain and 17 external links pointing to third-party websites. There are 22 external JavaScript files, 20 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 (@Ejabiah_CO), Instagram (@ejabiah_co), Linkedin (@positive-facilities-co-ltd), and Youtube (@Ejabiah_PF). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for ejabiah.com is well-optimized at 38 characters: "Ejabiah - Positive Facilities CO. LTD.". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for ejabiah.com. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as en and a favicon is configured. No Open Graph tags are configured. When someone shares a link to ejabiah.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.