celilove.com

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, celilove.com receives a trust score of 64/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, and DNSSEC providing authenticated DNS responses. 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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked celilove.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.

🤖 AI Summary

Our technology detection engine scanned celilove.com and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for celilove.com. Fonts: Google Fonts — delivers web fonts for typography for celilove.com.

🤖 AI Summary

celilove.com delivers its homepage in 2348ms (server response time), which is considered slow by industry standards. The total page weight is 15 KB, and we detected 34 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. 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. 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 celilove.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 15 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for celilove.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.

🤖 AI Summary

celilove.com resolves to the IPv4 address 104.21.83.190 and also supports IPv6 (2606:4700:3031::ac43:b4dc), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: adel.ns.cloudflare.com and miles.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. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for celilove.com, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 2 active subdomains for celilove.com: blog.celilove.com and www.celilove.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of celilove.com contains 1,061 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 1 H2 headings, 1 H3 headings, 2 H4 headings, 2 H5, and 3 H6 headings. The link structure consists of 21 internal links pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 0 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), Schema.org structured data (WebPage), and Progressive Web App (PWA) manifest (enabling app-like installation).

🤖 AI Summary

The title tag for celilove.com is good at 67 characters: "Site de rencontre sérieux et gratuit à l'inscription - Celilove.com". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 104 characters (well-optimized): "Site de rencontre simple, sérieux ♥ ♥ ♥ Inscription 100% gratuite pour tous. Bienvenue sur Celilove.com!". 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.celilove.com/, preventing duplicate content issues, the page language is declared as fr, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Site de rencontre gratuit - Celilove.com..."), OG description, OG image (social sharing thumbnail), 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 site implements Schema.org structured data with the following types: WebPage. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates. The meta keywords tag contains 6 terms including site de rencontre, gratuit, sérieux, homme, and femme. 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 celilove.com. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. No tracking IDs were detected on this page that could be used for cross-domain matching.