hommi.jp

We performed a comprehensive analysis of hommi.jp on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 9869ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 115 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 Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 8 domain(s) (Subject Alternative Names) and expires on 2026-10-29, which is 117 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 3 technologies across 3 categories powering hommi.jp. The detected stack includes Next.js css, React, and Webpack. The site uses Next.js as its primary framework (version css). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, hommi.jp receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, hommi.jp receives a trust score of 66/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 Amazon with 117 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 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, 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 hommi.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 hommi.jp and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version css) — provides the application framework and routing for hommi.jp. UI Library: React — handles the user interface rendering and component management for hommi.jp. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for hommi.jp.

hommi.jp delivers its homepage in 9869ms (server response time), which is considered slow by industry standards. The total page weight is 115 KB, and we detected 269 resource requests loading assets from 1 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 1 CSS files and 0 out of 8 JavaScript files are minified. Minifying the remaining 9 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 hommi.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 115 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for hommi.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.

hommi.jp resolves to the IPv4 address 108.156.22.109 and also supports IPv6 (2600:9000:2368:c00:f:1e8e:13c0:93a1), demonstrating modern network infrastructure readiness. The domain has 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1324.awsdns-37.org, ns-1994.awsdns-57.co.uk, ns-37.awsdns-04.com, and ns-641.awsdns-16.net. 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 hommi.jp is handled by Microsoft 365 with 1 MX records configured: hommi-jp.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 hommi.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 hommi.jp contains 552 words of visible text content. This is a moderate amount of content. The page is structured with 5 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 29 images. 1 images (3%) 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 97% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 175 internal links pointing to other pages on the same domain and 1 external link 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 8 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Schema.org structured data (SearchAction and WebSite). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on hommi.jp: Visa, Mastercard, American Express, Alipay, and JCB. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for hommi.jp is good at 25 characters: "Hommi-日本代购直邮-【全球包邮】日本代购网站". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 118 characters (well-optimized): "日本代购网站。提供日本零食、化妆品、护肤品、美容仪、生活用品等超过15000点商品，全部商品日本直邮，购满15000日元（约EUR81.27）免国际运费。网购日本商品，就来Hommi！支持国际信用卡，Paypal，支付宝等常用支付方式。". 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.hommi.jp/cn, preventing duplicate content issues, the page language is declared as zh-hans, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Hommi-日本代购直邮-【全球包邮】日本代购网站..."), OG description, 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. The site implements Schema.org structured data with the following types: 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.