ohsho.co.jp

We performed a comprehensive analysis of ohsho.co.jp on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 3044ms. 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 30 KB. 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.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-12-22, which is 175 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 1 technologies across 1 categories powering ohsho.co.jp. The detected stack includes jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ohsho.co.jp receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, ohsho.co.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 GlobalSign nv-sa with 175 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 ohsho.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 ohsho.co.jp 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. JavaScript Library: jQuery — provides utility functions and DOM manipulation for ohsho.co.jp.

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

ohsho.co.jp resolves to the IPv4 address 219.99.173.222, 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 1 A record(s) configured. The domain name system is managed by 2 name servers: ns0.future-s.com and ns1.future-s.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 ohsho.co.jp is handled by pphosted.com with 2 MX records configured: mxa-009b3401.gslb.pphosted.com and mxb-009b3401.gslb.pphosted.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 ohsho.co.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. Our subdomain enumeration scan discovered 1 active subdomains for ohsho.co.jp: www.ohsho.co.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of ohsho.co.jp contains 100 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 6 H2 headings, 3 H3 headings, 0 H4 headings. The page includes 61 images. 8 images (13%) 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 87% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 59 internal links pointing to other pages on the same domain and 26 external links pointing to third-party websites. There are 10 external JavaScript files, 5 CSS stylesheets, and 0 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 website has social media presence across 3 platforms: Facebook (@gyozaohsho), Twitter (@ohsho_campaign), and Youtube (@UCy_1uvlD0pt32HAG_klLhpA). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for ohsho.co.jp is good at 27 characters: "餃子の王将公式サイト | 株式会社 王将フ－ドサ－ビス". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 78 characters (well-optimized): "餃子の王将、公式サイトへようこそ！餃子へのこだわりから種類豊富な中華料理メニューのご紹介、お得なイベント・フェア情報まで。日本を美味しくする情報が満載です。". 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.ohsho.co.jp/, preventing duplicate content issues, the page language is declared as ja, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("餃子の王将 公式サイト..."), OG description, OG image (social sharing thumbnail), 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 meta keywords tag contains 4 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.