b2b.rawlings.com

We performed a comprehensive analysis of b2b.rawlings.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 21806ms. The page is served over HTTP/1.1 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 138 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 85/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing 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 b2b.rawlings.com. The detected stack includes Angular, Bootstrap 4.3.1, PayPal, Cloudflare, StackPath, Google Fonts, jQuery, and Font Awesome. The site uses Angular as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, b2b.rawlings.com receives an overall trust score of 67/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, b2b.rawlings.com receives a trust score of 67/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 and HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks. 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 b2b.rawlings.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.

Our technology detection engine scanned b2b.rawlings.com 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. Framework: Angular — provides the application framework and routing for b2b.rawlings.com. CSS Framework: Bootstrap (version 4.3.1) — provides the styling and responsive layout system for b2b.rawlings.com. Payments: PayPal — processes payment transactions for b2b.rawlings.com. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for b2b.rawlings.com. Fonts: Google Fonts — delivers web fonts for typography for b2b.rawlings.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for b2b.rawlings.com. Icon Set: Font Awesome — provides additional functionality for b2b.rawlings.com.

b2b.rawlings.com delivers its homepage in 21806ms (server response time), which is considered slow by industry standards. The total page weight is 138 KB, and we detected 148 resource requests loading assets from 10 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 b2b.rawlings.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: 5 out of 8 CSS files and 12 out of 28 JavaScript files are minified. Minifying the remaining 19 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 b2b.rawlings.com produces approximately 0.07g 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 138 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for b2b.rawlings.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.

b2b.rawlings.com resolves to the IPv4 address 104.18.30.220 and also supports IPv6 (2606:4700::6812:1fdc), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. 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 not enabled for b2b.rawlings.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 homepage of b2b.rawlings.com contains 344 words of visible text content. This is a moderate amount of content. The page is structured with 8 H2 headings, 0 H3 headings, 5 H4 headings, 28 H5, and 0 H6 headings. The page includes 11 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 77 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. There are 28 external JavaScript files, 8 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for b2b.rawlings.com is good at 4 characters: "Home". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for b2b.rawlings.com. 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://dealer.rawlings.com, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Home..."), 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.