dice.fm

We performed a comprehensive analysis of dice.fm on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 42799ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 297 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 18 domain(s) (Subject Alternative Names) and expires on 2026-09-21, which is 81 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 9 technologies across 7 categories powering dice.fm. The detected stack includes Next.js chunks, React, Vite, Google Analytics 4, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Zendesk, and reCAPTCHA v3. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, dice.fm receives an overall trust score of 72/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, dice.fm receives a trust score of 72/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, a valid SSL certificate issued by Google Trust Services with 81 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, DNSSEC providing authenticated DNS responses, and a well-established domain registered for over 12.7 years, indicating long-term commitment and legitimacy. 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 dice.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. The domain is registered through Instra Corporation Pty Ltd. based in CA, with a registration date of 2013-11-01 and expiration date of 2026-11-01.

Our technology detection engine scanned dice.fm and identified 9 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. Framework: Next.js (version chunks) — provides the application framework and routing for dice.fm. UI Library: React — handles the user interface rendering and component management for dice.fm. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for dice.fm. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for dice.fm. Advertising: Meta Pixel, TikTok Pixel, and LinkedIn Insight Tag — handles advertising pixel tracking and conversion measurement for dice.fm. Support: Zendesk — handles customer support tickets and knowledge bases for dice.fm. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for dice.fm. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-RGC53CX1F7 and TikTok Pixel ID CK4SNTJC77U0C3LA0CEG. These IDs can be used to identify other websites operated by the same organization.

dice.fm delivers its homepage in 42799ms (server response time), which is considered slow by industry standards. The total page weight is 297 KB, and we detected 139 resource requests loading assets from 15 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: 0 out of 1 CSS files and 0 out of 40 JavaScript files are minified. Minifying the remaining 41 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. 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 dice.fm 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 297 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for dice.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.

dice.fm resolves to the IPv4 address 104.18.31.9 and also supports IPv6 (2606:4700::6812:1f09), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: amir.ns.cloudflare.com and fiona.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. Email for dice.fm is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 dice.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 domain is registered through Instra Corporation Pty Ltd. (CA). It was first registered on 2013-11-01 and is set to expire on 2026-11-01, making it 12.7 years old. Our subdomain enumeration scan discovered 5 active subdomains for dice.fm: api.dice.fm, app.dice.fm, blog.dice.fm, m.dice.fm, and www.dice.fm. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of dice.fm contains 268 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 9 H2 headings, 0 H3 headings, 0 H4 headings, 3 H5, and 0 H6 headings. The page includes 15 images. 10 images (67%) 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 33% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 23 internal links pointing to other pages on the same domain and 9 external links pointing to third-party websites. There are 40 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior), Schema.org structured data (Brand, SearchAction, and WebSite), and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on dice.fm: Discover, JCB, Apple Pay, and Google Pay. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 6 platforms: Facebook (@tr), Twitter (@uwt.js), Instagram (@dicefm), Linkedin (@dice-fm), Youtube (@dice_fm), and Tiktok (@dice.fm). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for dice.fm is well-optimized at 37 characters: "DICE | Tickets for your kind of shows". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 149 characters (well-optimized): "We’ll get you out more. We bring the best live events to people around the world. See what concerts, tours, and festival...". 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://dice.fm, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to index,follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("DICE | Tickets for your kind of shows..."), 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: Brand, SearchAction, 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. The meta keywords tag contains 13 terms including DICE, DICE App, DICE FM, Music, and Gigs. 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.