stat.ink

We performed a comprehensive analysis of stat.ink on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 7619ms. 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 126 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 Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-26, which is 57 days from now. The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing Content-Security-Policy, 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 4 technologies across 4 categories powering stat.ink. The detected stack includes Bootstrap, GitHub Pages, Google Fonts, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, stat.ink receives an overall trust score of 79/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, stat.ink receives a trust score of 79/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, a valid SSL certificate issued by Google Trust Services with 57 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DNSSEC providing authenticated DNS responses, and a well-established domain registered for over 10.8 years, indicating long-term commitment and legitimacy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked stat.ink 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. The domain is registered through Cloudflare, Inc. based in CA, with a registration date of 2015-09-24 and expiration date of 2026-09-24.

Our technology detection engine scanned stat.ink and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CSS Framework: Bootstrap — provides the styling and responsive layout system for stat.ink. Hosting: GitHub Pages — provides the server infrastructure for stat.ink. Fonts: Google Fonts — delivers web fonts for typography for stat.ink. JavaScript Library: jQuery — provides utility functions and DOM manipulation for stat.ink.

stat.ink delivers its homepage in 7619ms (server response time), which is considered slow by industry standards. The total page weight is 126 KB, and we detected 215 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 stat.ink. 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: 10 out of 21 CSS files and 3 out of 21 JavaScript files are minified. Minifying the remaining 29 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 stat.ink 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 126 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for stat.ink. 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.

stat.ink resolves to the IPv4 address 104.21.30.97 and also supports IPv6 (2606:4700:3035::6815:1e61), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: scott.ns.cloudflare.com and vida.ns.cloudflare.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 stat.ink is handled by fetus.jp with 2 MX records configured: mail.fetus.jp and mx-bk1.fetus.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 enabled for stat.ink, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. The domain is registered through Cloudflare, Inc. (CA). It was first registered on 2015-09-24 and is set to expire on 2026-09-24, making it 10.8 years old. Our subdomain enumeration scan discovered 2 active subdomains for stat.ink: dev.stat.ink and www.stat.ink. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of stat.ink contains 1,255 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 0 H2 headings, 0 H3 headings, 3 H4 headings. The page includes 36 images. 11 images (31%) 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 69% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 55 internal links pointing to other pages on the same domain and 53 external links pointing to third-party websites. There are 21 external JavaScript files, 21 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 2 platforms: Twitter (@SplatoonJP) and Github (@frozenpandaman). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for stat.ink is good at 8 characters: "stat.ink". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for stat.ink. 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 page language is declared as en-us and a favicon is configured. No Open Graph tags are configured. When someone shares a link to stat.ink on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. 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.