450.fm

We performed a comprehensive analysis of 450.fm on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 10606ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 606 KB. Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. 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 8 technologies across 7 categories powering 450.fm. The detected stack includes WordPress, Vite, Google Analytics 4, Matomo, reCAPTCHA v3, Google Fonts, jQuery, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 450.fm receives an overall trust score of 61/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, 450.fm receives a trust score of 61/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 none policy, 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 450.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 450.fm and identified 8 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. CMS: WordPress — manages the content and page structure for 450.fm. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for 450.fm. Analytics: Google Analytics 4 and Matomo — tracks visitor behavior and provides traffic insights for 450.fm. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for 450.fm. Fonts: Google Fonts — delivers web fonts for typography for 450.fm. JavaScript Library: jQuery — provides utility functions and DOM manipulation for 450.fm. Icon Set: Font Awesome — provides additional functionality for 450.fm. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-F4VVK8J32T. These IDs can be used to identify other websites operated by the same organization.

450.fm resolves to the IPv4 address 178.32.177.201, 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: dns13.ovh.net and ns13.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 450.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 (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 enabled for 450.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. Our subdomain enumeration scan discovered 1 active subdomains for 450.fm: www.450.fm. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for 450.fm is well-optimized at 53 characters: "Accueil - 450.fm - Journal n°1 de la Franc-maçonnerie". 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 450.fm. 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 canonical url is correctly set to https://450.fm/, preventing duplicate content issues, the page language is declared as fr-fr, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Accueil - 450.fm - Journal n°1 de la Franc-maçonnerie..."), 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. 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. The site implements Schema.org structured data with the following types: BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite. 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.