radio.immo

We performed a comprehensive analysis of radio.immo on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 29307ms. The page is served over HTTP/2 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 306 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 3 domain(s) (Subject Alternative Names) and expires on 2026-10-04, which is 89 days from now. The security headers analysis reveals a score of 85/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing X-Frame-Options, 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 radio.immo. The detected stack includes React, Google Analytics 4, Matomo, Google Fonts, and jQuery 1.11.1.. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, radio.immo receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, radio.immo receives a trust score of 80/100, which places it in the "Very 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, a valid SSL certificate issued by Let's Encrypt with 89 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 radio.immo 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 radio.immo 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. UI Library: React — handles the user interface rendering and component management for radio.immo. Analytics: Google Analytics 4 and Matomo — tracks visitor behavior and provides traffic insights for radio.immo. Fonts: Google Fonts — delivers web fonts for typography for radio.immo. JavaScript Library: jQuery (version 1.11.1.) — provides utility functions and DOM manipulation for radio.immo. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-RGL2HX8YXZ. These IDs can be used to identify other websites operated by the same organization.

radio.immo delivers its homepage in 29307ms (server response time), which is considered slow by industry standards. The total page weight is 306 KB, and we detected 485 resource requests loading assets from 78 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 radio.immo. 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: 0 out of 8 CSS files and 0 out of 29 JavaScript files are minified. Minifying the remaining 37 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 radio.immo produces approximately 0.15g 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 306 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for radio.immo. 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.

radio.immo resolves to the IPv4 address 51.210.38.0, 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 4 name servers: ns-fr.1and1-dns.biz, ns-fr.1and1-dns.com, ns-fr.1and1-dns.fr, and ns-fr.1and1-dns.org. Having 4 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 radio.immo is handled by ionos.fr with 2 MX records configured: mx00.ionos.fr and mx01.ionos.fr. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 radio.immo. 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 radio.immo contains 2,458 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 28 H2 headings, 6 H3 headings, 3 H4 headings, 3 H5, and 0 H6 headings. The page includes 169 images. 37 images (22%) 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 78% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 229 internal links pointing to other pages on the same domain and 90 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 29 external JavaScript files, 8 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), and RSS feed for content syndication. Notable missing features: 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 (@radioimmo.fr), Twitter (@radioimmo), Instagram (@radioimmo), Youtube (@lucky88ltd), and Pinterest (@lucky88ltd). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for radio.immo is well-optimized at 59 characters: "Radio-immo.fr - Premiere webradio d'information immobiliere". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 43 characters (acceptable): "Premiere webradio d'information immobiliere". 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 page language is declared as fr, the meta robots directive is set to max-snippet:-1,max-video-preview:-1,max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Radio-immo.fr..."), OG description, OG image (social sharing thumbnail), These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.