kj.com

We performed a comprehensive analysis of kj.com on 2026-07-08. The website returned an HTTP 200 status code with a server response time of 11973ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 239 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 Sectigo Limited (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 48 domain(s) (Subject Alternative Names) and expires on 2026-10-05, which is 89 days from now. 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 1 technologies across 1 categories powering kj.com. The detected stack includes Google Tag Manager. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, kj.com receives an overall trust score of 71/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, kj.com receives a trust score of 71/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 Sectigo Limited with 89 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine 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 kj.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 kj.com and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for kj.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-M6X2X9T2. These IDs can be used to identify other websites operated by the same organization.

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

kj.com resolves to the IPv4 address 104.21.61.77 and also supports IPv6 (2606:4700:3032::ac43:cf62), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: deb.ns.cloudflare.com and mario.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 kj.com is handled by Microsoft 365 with 1 MX records configured: kj-com.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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 kj.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 kj.com contains 940 words of visible text content. This is a moderate amount of content. The page is structured with 7 H2 headings, 6 H3 headings, 2 H4 headings, 2 H5, and 0 H6 headings. The page includes 26 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 133 internal links pointing to other pages on the same domain and 8 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 15 external JavaScript files, 8 CSS stylesheets, and 1 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. We detected the following payment methods accepted on kj.com: Discover and Apple 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 5 platforms: Facebook (@kjwines), Twitter (@KJWines), Instagram (@kjwines), Youtube (@UCBx0mZ3puIe7dZok8LgtDoA), and Pinterest (@kjwines). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for kj.com is well-optimized at 54 characters: "Kendall-Jackson Wines | California-Grown, Family-Owned". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 190 characters (slightly long): "The official website of Kendall-Jackson Wines. Located in the heart of Sonoma County Wine Country, producing sustainably...". 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.kj.com/, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to kj.com 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 4 terms including Kendall-Jackson, wine, wines, and California. 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.