raceroster.com

We performed a comprehensive analysis of raceroster.com on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 23568ms. 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 112 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 Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-11-27, which is 148 days from now. The security headers analysis reveals a score of 100/100 (excellent). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. All recommended security headers are in place, providing comprehensive protection against common web attacks. Our technology detection scan identified 6 technologies across 6 categories powering raceroster.com. The detected stack includes WordPress, Google Analytics 4, Google Tag Manager, reCAPTCHA v3, Google Fonts, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, raceroster.com receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, raceroster.com 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 Amazon with 148 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and a well-established domain registered for over 14.8 years, indicating long-term commitment and legitimacy. Areas of concern include: 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 raceroster.com 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 GoDaddy.com, LLC based in US, with a registration date of 2011-09-21 and expiration date of 2026-09-21.

Our technology detection engine scanned raceroster.com and identified 6 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: WordPress — manages the content and page structure for raceroster.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for raceroster.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for raceroster.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for raceroster.com. Fonts: Google Fonts — delivers web fonts for typography for raceroster.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for raceroster.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-T7T88D8. These IDs can be used to identify other websites operated by the same organization.

raceroster.com delivers its homepage in 23568ms (server response time), which is considered slow by industry standards. The total page weight is 112 KB, and we detected 121 resource requests loading assets from 7 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 raceroster.com. 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 2 CSS files and 2 out of 4 JavaScript files are minified. Minifying the remaining 4 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 raceroster.com produces approximately 0.05g 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 112 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for raceroster.com. 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.

raceroster.com resolves to the IPv4 address 13.33.235.63 and also supports IPv6 (2600:9000:20a8:6e00:15:9178:6a80:93a1), demonstrating modern network infrastructure readiness. The domain has 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1103.awsdns-09.org, ns-1939.awsdns-50.co.uk, ns-218.awsdns-27.com, and ns-834.awsdns-40.net. 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 raceroster.com is handled by mimecast.com with 2 MX records configured: de-smtp-inbound-1.mimecast.com and de-smtp-inbound-2.mimecast.com. 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 raceroster.com. 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 domain is registered through GoDaddy.com, LLC (US). It was first registered on 2011-09-21 and is set to expire on 2026-09-21, making it 14.8 years old. Our subdomain enumeration scan discovered 10 active subdomains for raceroster.com: admin.raceroster.com, api.raceroster.com, app.raceroster.com, blog.raceroster.com, cdn.raceroster.com, dev.raceroster.com, m.raceroster.com, and mail.raceroster.com. Plus 2 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of raceroster.com contains 1,294 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 6 H2 headings, 7 H3 headings, 0 H4 headings. The page includes 20 images. 17 images (85%) 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 15% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 84 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 4 external JavaScript files, 2 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Schema.org structured data (BreadcrumbList, EntryPoint, ImageObject, ListItem, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@RaceRoster), Twitter (@RaceRoster), and Instagram (@raceroster). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for raceroster.com is too long at 85 characters: "Race Roster - Create a race event with our free event registration tool — Race R...". At 85 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 132 characters (well-optimized): "A comprehensive set of tools designed to meet the unique needs of event organizers, timers, and fundraising coordinators...". 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://raceroster.com/, preventing duplicate content issues, the page language is declared as en-ca, 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 4/4 recommended fields: OG title ("Race Roster - Create a race event with our free event regist..."), 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. 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, 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.