giginc.co.jp

We performed a comprehensive analysis of giginc.co.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 23470ms. The page is served over HTTP/2 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 44 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 35/100 (below average). The following security headers are properly configured: Strict-Transport-Security (HSTS) and X-Content-Type-Options. However, the site is missing Content-Security-Policy, X-Frame-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 giginc.co.jp. The detected stack includes Google Analytics 4, Microsoft Clarity, Google Tag Manager, HubSpot, reCAPTCHA v3, Cloudflare, and jQuery 3.4.1.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, giginc.co.jp receives an overall trust score of 70/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, giginc.co.jp receives a trust score of 70/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. 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 giginc.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 giginc.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. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for giginc.co.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for giginc.co.jp. Marketing: HubSpot — provides marketing automation capabilities for giginc.co.jp. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for giginc.co.jp. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for giginc.co.jp. JavaScript Library: jQuery (version 3.4.1.) — provides utility functions and DOM manipulation for giginc.co.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-TSGZ5BT. These IDs can be used to identify other websites operated by the same organization.

giginc.co.jp delivers its homepage in 23470ms (server response time), which is considered slow by industry standards. The total page weight is 44 KB, and we detected 140 resource requests loading assets from 22 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 giginc.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: 1 out of 4 CSS files and 3 out of 15 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. 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 giginc.co.jp produces approximately 0.02g 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 44 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for giginc.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.

giginc.co.jp resolves to the IPv4 address 18.165.140.42, 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 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1497.awsdns-59.org, ns-1643.awsdns-13.co.uk, ns-624.awsdns-14.net, and ns-77.awsdns-09.com. 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 giginc.co.jp is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for giginc.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 giginc.co.jp: portal.giginc.co.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of giginc.co.jp contains 192 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, 0 H3 headings, 0 H4 headings. The page includes 33 images. 20 images (61%) 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 39% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 68 internal links pointing to other pages on the same domain and 16 external links pointing to third-party websites. There are 15 external JavaScript files, 4 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 website has social media presence across 3 platforms: Facebook (@gig2016), Twitter (@giginc2016), and Instagram (@giginc.official). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for giginc.co.jp is good at 29 characters: "東京のWEB制作会社・ホームページ制作会社｜株式会社GIG". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 122 characters (well-optimized): "株式会社GIGは東京のWEB制作、ホームページ制作会社、システム開発会社です。WEBサイトやメディアサイトの企画・制作・運用、WEBマーケティング、システム開発、体制構築、及び人工知能をかけ合わせたライフスタイル領域のサービスを開発していま...". 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 page language is declared as ja and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("東京のWEB制作会社・ホームページ制作会社｜株式会社GIG..."), 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. 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.