rci.fm

We performed a comprehensive analysis of rci.fm on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 12509ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 43 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-12, which is 44 days from now. The security headers analysis reveals a score of 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 6 categories powering rci.fm. The detected stack includes Drupal, Bootstrap 4.3.1, Google Analytics 4, Google Tag Manager, Cloudflare, StackPath, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, rci.fm receives an overall trust score of 70/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, rci.fm receives a trust score of 70/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 Let's Encrypt with 44 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, 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, 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 rci.fm 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 rci.fm and identified 7 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: Drupal — manages the content and page structure for rci.fm. CSS Framework: Bootstrap (version 4.3.1) — provides the styling and responsive layout system for rci.fm. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for rci.fm. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for rci.fm. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for rci.fm. JavaScript Library: jQuery — provides utility functions and DOM manipulation for rci.fm. We also extracted the following tracking identifiers: Google Tag Manager container GTM-N5TSDM9. These IDs can be used to identify other websites operated by the same organization.

rci.fm delivers its homepage in 12509ms (server response time), which is considered slow by industry standards. The total page weight is 43 KB, and we detected 155 resource requests loading assets from 13 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: 3 out of 71 CSS files and 7 out of 45 JavaScript files are minified. Minifying the remaining 106 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 rci.fm produces approximately 0.02g 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 43 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for rci.fm. 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.

rci.fm resolves to the IPv4 address 137.74.206.23, 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: dns18.ovh.net and ns18.ovh.net. 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 rci.fm is handled by ovh.net with 3 MX records configured: mx1.mail.ovh.net, mx2.mail.ovh.net, and mx3.mail.ovh.net. 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 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 rci.fm, 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.

The homepage of rci.fm contains 43 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 0 H2 headings, 0 H3 headings, 1 H4 headings. The page includes 8 images. 7 images (88%) 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 12% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 8 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 45 external JavaScript files, 71 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for rci.fm is well-optimized at 32 characters: "Toute l'info de la Caraïbe | RCI". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 143 characters (well-optimized): "Découvrez l'actu en continu de la Guadeloupe et de la Martinique. Écoutez la radio en direct et les replays de vos émiss...". 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://rci.fm/deuxiles/landing, preventing duplicate content issues, the page language is declared as fr, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Toute l'info de la Caraïbe | RCI..."), 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.