radiofm.rs

We performed a comprehensive analysis of radiofm.rs on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 3867ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 24 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by DigiCert Inc (OV 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-11-03, which is 126 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 5 technologies across 5 categories powering radiofm.rs. The detected stack includes Bootstrap 3.3.7, Google Analytics 4, Google AdSense, StackPath, and jQuery 3.2.1.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, radiofm.rs receives an overall trust score of 65/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, radiofm.rs receives a trust score of 65/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 DigiCert Inc with 126 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, 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 radiofm.rs 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 radiofm.rs and identified 5 distinct technologies across 5 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 (version 3.3.7) — provides the styling and responsive layout system for radiofm.rs. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for radiofm.rs. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for radiofm.rs. CDN: StackPath — accelerates content delivery by caching assets at edge locations worldwide for radiofm.rs. JavaScript Library: jQuery (version 3.2.1.) — provides utility functions and DOM manipulation for radiofm.rs.

radiofm.rs delivers its homepage in 3867ms (server response time), which is considered slow by industry standards. The total page weight is 24 KB, and we detected 186 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: 1 out of 3 CSS files and 2 out of 8 JavaScript files are minified. Minifying the remaining 8 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 radiofm.rs 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 24 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for radiofm.rs. 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.

radiofm.rs resolves to the IPv4 address 93.188.2.55 and also supports IPv6 (2a02:250:0:8::56), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: ns1.loopia.se and ns2.loopia.se. 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 radiofm.rs is handled by loopia.se with 2 MX records configured: mailcluster.loopia.se and mail2.loopia.se. 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 radiofm.rs, 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 radiofm.rs: mail.radiofm.rs and www.radiofm.rs. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of radiofm.rs contains 89 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, 0 H4 headings. The page includes 87 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 80 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. There are 8 external JavaScript files, 3 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) 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 radiofm.rs is good at 26 characters: "Radio stanice Srbije uživo". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 49 characters (acceptable): "Najslušanije radio stanice Srbije na jednom mestu". 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 sr and a favicon is configured. No Open Graph tags are configured. When someone shares a link to radiofm.rs 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. The meta keywords tag contains 11 terms including Radio, Radio stanice, Radio stanice Srbije, domaće radio stanice, and slušaj radio uživo. 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.