gillandco.jp

We performed a comprehensive analysis of gillandco.jp on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 35786ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 187 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV 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-09-20, which is 80 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 6 technologies across 6 categories powering gillandco.jp. The detected stack includes WordPress, WooCommerce, Webpack, Google Analytics 4, reCAPTCHA v3, and jQuery. The primary e-commerce platform is WooCommerce. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, gillandco.jp receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, gillandco.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 Let's Encrypt with 80 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a reject policy — the strongest available setting. 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 gillandco.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 gillandco.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. CMS: WordPress — manages the content and page structure for gillandco.jp. Ecommerce: WooCommerce — powers the online store and shopping functionality for gillandco.jp. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for gillandco.jp. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for gillandco.jp. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for gillandco.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for gillandco.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-85K3SQVZDP. These IDs can be used to identify other websites operated by the same organization.

gillandco.jp delivers its homepage in 35786ms (server response time), which is considered slow by industry standards. The total page weight is 187 KB, and we detected 91 resource requests loading assets from 5 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: 15 out of 28 CSS files and 20 out of 22 JavaScript files are minified. Minifying the remaining 15 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 gillandco.jp produces approximately 0.09g 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 187 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for gillandco.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.

gillandco.jp resolves to the IPv4 address 183.90.240.41, 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 5 name servers: ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, and ns5.xserver.jp. Having 5 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 gillandco.jp is handled by gillandco.jp with 1 MX records configured: gillandco.jp. 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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. 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 gillandco.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 gillandco.jp contains 507 words of visible text content. This is a moderate amount of content. The page is structured with 9 H2 headings, 4 H3 headings, 0 H4 headings. The page includes 12 images. 11 images (92%) 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 8% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 15 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 22 external JavaScript files, 28 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), robots.txt (controls search engine crawling behavior), Schema.org structured data (BreadcrumbList, ListItem, Organization, WebPage, and WebSite), and RSS feed for content syndication. The website has social media presence across 1 platforms: Facebook (@gillandco802). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for gillandco.jp is well-optimized at 54 characters: "小倉 焼き鳥 Gillandco 小倉駅3から徒歩３分 Best Yakitori Grill Kokura". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 223 characters (slightly long): "Best Yakitori Grill Kokura! 小倉 焼き鳥 小倉駅徒歩３分。テーブル席あり。日本酒が充実。営業時間 16:00-23:00 | Authentic Japanese Yakitori restaurant in K...". 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://gillandco.jp/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("小倉 焼き鳥 Gillandco 小倉駅3から徒歩３分 Best Yakitori Grill Kokura..."), OG description, OG type (article). 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_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: BreadcrumbList, ListItem, Organization, WebPage, 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.