peakpine.jp

We performed a comprehensive analysis of peakpine.jp on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 16605ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 4.0% size reduction. The total page weight is 76 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 GlobalSign nv-sa (OV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES128-GCM-SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-12-10, which is 160 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Strict-Transport-Security (HSTS) 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 6 technologies across 6 categories powering peakpine.jp. The detected stack includes Google Analytics 4, Google Tag Manager, Meta Pixel, Akamai, Google Fonts, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, peakpine.jp receives an overall trust score of 76/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, peakpine.jp receives a trust score of 76/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 GlobalSign nv-sa with 160 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. 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 peakpine.jp 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 peakpine.jp 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. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for peakpine.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for peakpine.jp. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for peakpine.jp. CDN: Akamai — accelerates content delivery by caching assets at edge locations worldwide for peakpine.jp. Fonts: Google Fonts — delivers web fonts for typography for peakpine.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for peakpine.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-VQQTCDPHVY, Google Tag Manager container GTM-M5FH3TC, and Meta (Facebook) Pixel ID 1018571025798560. These IDs can be used to identify other websites operated by the same organization.

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

peakpine.jp resolves to the IPv4 address 35.77.238.240, 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 2 A record(s) configured. The domain name system is managed by 3 name servers: ns1.sixcore.ne.jp, ns2.sixcore.ne.jp, and ns3.sixcore.ne.jp. Having 3 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 peakpine.jp is handled by Google Workspace with 1 MX records configured: SMTP.GOOGLE.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 peakpine.jp. 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 peakpine.jp contains 274 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 5 H2 headings, 7 H3 headings, 11 H4 headings. The page includes 71 images. 25 images (35%) 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 65% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 106 internal links pointing to other pages on the same domain and 2 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 11 external JavaScript files, 9 CSS stylesheets, and 1 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on peakpine.jp: Visa and JCB. 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 1 platforms: Facebook (@tr). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for peakpine.jp is good at 29 characters: "純ゲルマニウム製品なら｜純日本製ゲルマニウム ピークパイン". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 63 characters (acceptable): "【公式】1964年創業 職人の手作業の加工。純ゲルマニウムのピークパイン公式通販。各種健康関連商品の製造販売。/（株高千穂金属". 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.peakpine.jp/, preventing duplicate content issues. No Open Graph tags are configured. When someone shares a link to peakpine.jp 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.