geiko.app

We performed a comprehensive analysis of geiko.app on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 4137ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 89 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-01, which is 63 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 10 technologies across 8 categories powering geiko.app. The detected stack includes WordPress, Google Analytics 4, Google Tag Manager, reCAPTCHA v3, Cloudflare, StackPath, Google Fonts, Adobe Fonts, jQuery, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, geiko.app receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, geiko.app receives a trust score of 60/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 and a valid SSL certificate issued by Let's Encrypt with 63 days until expiration. 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 geiko.app 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 geiko.app and identified 10 distinct technologies across 8 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 geiko.app. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for geiko.app. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for geiko.app. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for geiko.app. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for geiko.app. Fonts: Google Fonts and Adobe Fonts — delivers web fonts for typography for geiko.app. JavaScript Library: jQuery — provides utility functions and DOM manipulation for geiko.app. Icon Set: Font Awesome — provides additional functionality for geiko.app. We also extracted the following tracking identifiers: Google Tag Manager container GTM-K32ZKSC. These IDs can be used to identify other websites operated by the same organization.

geiko.app delivers its homepage in 4137ms (server response time), which is considered slow by industry standards. The total page weight is 89 KB, and we detected 156 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: 5 out of 17 CSS files and 9 out of 15 JavaScript files are minified. Minifying the remaining 18 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 geiko.app produces approximately 0.04g 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 89 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for geiko.app. 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.

geiko.app resolves to the IPv4 address 202.254.239.159, 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 4 name servers: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, and 04.dnsv.jp. 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 geiko.app is handled by geiko.app with 1 MX records configured: geiko.app. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 geiko.app. 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 geiko.app contains 193 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 17 H2 headings, 0 H3 headings, 2 H4 headings. The page includes 36 images. 30 images (83%) 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 17% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 65 internal links pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 15 external JavaScript files, 17 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), and RSS feed for content syndication. Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for geiko.app is good at 26 characters: "芸工アプリ メディア | みんなでつくろう芸工アプリ". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for geiko.app. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The canonical url is correctly set to https://geiko.app/, 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 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. 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.