reebok.mx

We performed a comprehensive analysis of reebok.mx on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 6494ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 474 KB, and the site is served behind a CDN (Content Delivery Network). 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 35/100 (below average). The following security headers are properly configured: Content-Security-Policy and X-Content-Type-Options. However, the site is missing Strict-Transport-Security (HSTS), X-Frame-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 7 technologies across 7 categories powering reebok.mx. The detected stack includes Google Analytics 4, Google Tag Manager, VWO, Salesforce, reCAPTCHA v3, jQuery, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, reebok.mx receives an overall trust score of 64/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, reebok.mx receives a trust score of 64/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, 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), missing Referrer-Policy, potentially leaking URL information to third parties, 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 reebok.mx 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 reebok.mx and identified 7 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. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for reebok.mx. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for reebok.mx. A/B Testing: VWO — enables experimentation and conversion optimization for reebok.mx. CRM: Salesforce — manages customer relationships and sales pipelines for reebok.mx. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for reebok.mx. JavaScript Library: jQuery — provides utility functions and DOM manipulation for reebok.mx. Icon Set: Font Awesome — provides additional functionality for reebok.mx. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-TENIS and Google Tag Manager container GTM-KB2FWG7. These IDs can be used to identify other websites operated by the same organization.

reebok.mx delivers its homepage in 6494ms (server response time), which is considered slow by industry standards. The total page weight is 474 KB, and we detected 563 resource requests loading assets from 9 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 13 CSS files and 2 out of 14 JavaScript files are minified. Minifying the remaining 25 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 reebok.mx produces approximately 0.23g of CO₂, earning a carbon rating of B. 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 474 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for reebok.mx. 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.

reebok.mx resolves to the IPv4 address 3.33.139.32, 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: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, and ha4.markmonitor.zone. 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 reebok.mx is handled by Microsoft 365 with 1 MX records configured: reebok-mx.mail.protection.outlook.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 reebok.mx. 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. Our subdomain enumeration scan discovered 1 active subdomains for reebok.mx: www.reebok.mx. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of reebok.mx contains 1,166 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 5 H2 headings, 11 H3 headings, 41 H4 headings. The page includes 116 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 376 internal links pointing to other pages on the same domain and 6 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 14 external JavaScript files, 13 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: Schema.org structured data (DataCatalog, Dataset, SearchAction, and WebSite). Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@ReebokMexico), Twitter (@api), and Instagram (@reebokmx). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for reebok.mx is well-optimized at 40 characters: "Ropa, Tenis y Accesorios | Reebok México". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 111 characters (well-optimized): "Explora la variedad de tenis, ropa y accesorios en Reebok México, como: nano x4, floatzig, court advance y más!". 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://www.reebok.mx, preventing duplicate content issues, the page language is declared as es, the meta robots directive is set to index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Ropa, Tenis y Accesorios | Reebok México..."), 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: DataCatalog, Dataset, 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 5 terms including tennis, padel, deporte, ropa deportiva, and calzado. 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.