become.co.jp

We performed a comprehensive analysis of become.co.jp on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 11915ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 119 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 Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-09-05, which is 60 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-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 6 categories powering become.co.jp. The detected stack includes Bootstrap 3.3.6, Google Analytics 4, Microsoft Clarity, Google Tag Manager, Cloudflare, jQuery, and WP Rocket. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, become.co.jp receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, become.co.jp receives a trust score of 68/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 Google Trust Services with 60 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked become.co.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 become.co.jp and identified 7 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. CSS Framework: Bootstrap (version 3.3.6) — provides the styling and responsive layout system for become.co.jp. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for become.co.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for become.co.jp. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for become.co.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for become.co.jp. Performance: WP Rocket — optimizes page loading speed and performance for become.co.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-BC0P0GGSYW and Google Tag Manager container GTM-MLSND2GP. These IDs can be used to identify other websites operated by the same organization.

become.co.jp delivers its homepage in 11915ms (server response time), which is considered slow by industry standards. The total page weight is 119 KB, and we detected 264 resource requests loading assets from 12 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: 1 out of 3 CSS files and 9 out of 17 JavaScript files are minified. Minifying the remaining 10 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 become.co.jp produces approximately 0.06g 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 119 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for become.co.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.

become.co.jp resolves to the IPv4 address 172.67.68.126 and also supports IPv6 (2606:4700:20::681a:d6f), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: ernest.ns.cloudflare.com and liv.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 become.co.jp is handled by cloudflare.net with 3 MX records configured: route3.mx.cloudflare.net, route1.mx.cloudflare.net, and route2.mx.cloudflare.net. 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 enabled for become.co.jp, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.

The homepage of become.co.jp contains 541 words of visible text content. This is a moderate amount of content. The page is structured with 4 H2 headings, 0 H3 headings, 29 H4 headings. The page includes 49 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 106 internal links pointing to other pages on the same domain and 33 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 17 external JavaScript files, 3 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for become.co.jp is good at 13 characters: "通販検索・価格比較のビカム". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 126 characters (well-optimized): "探しものは何ですか♪ 価格比較サイトのビカムは、全国の通販ショップから、いま大人気の格安・激安商品を、ランキングや口コミを元に徹底比較。ファッション、家電などあらゆるジャンルから、1500万点以上の商品、3万店以上の通販ショップ情報を一括検...". 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.become.co.jp/, preventing duplicate content issues, the page language is declared as jp, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("通販検索・価格比較のビカム..."), OG description, OG image (social sharing thumbnail), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The meta keywords tag contains 7 terms including 通販, 価格, 比較, 人気, and 格安. 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.