inkstory.net

We performed a comprehensive analysis of inkstory.net on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 13384ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 315 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_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 3 domain(s) (Subject Alternative Names) and expires on 2026-07-31, which is 31 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Content-Security-Policy. However, the site is missing 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 2 technologies across 2 categories powering inkstory.net. The detected stack includes Astro and Google Analytics 4. The site uses Astro as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, inkstory.net receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, inkstory.net 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 31 days until expiration. Areas of concern include: 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 inkstory.net 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 PDR Ltd. d/b/a PublicDomainRegistry.com based in BZ, with a registration date of 2025-09-18 and expiration date of 2026-09-18.

Our technology detection engine scanned inkstory.net and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Astro — provides the application framework and routing for inkstory.net. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for inkstory.net. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-KFYMF6CKGB. These IDs can be used to identify other websites operated by the same organization.

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

inkstory.net resolves to the IPv4 address 190.115.16.33, 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: dee.ns.cloudflare.com and lou.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. 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 inkstory.net. 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 domain is registered through PDR Ltd. d/b/a PublicDomainRegistry.com (BZ). It was first registered on 2025-09-18 and is set to expire on 2026-09-18, making it 0.8 years old. Our subdomain enumeration scan discovered 2 active subdomains for inkstory.net: api.inkstory.net and www.inkstory.net. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of inkstory.net contains 849 words of visible text content. This is a moderate amount of content. The page is structured with 7 H2 headings, 3 H3 headings, 0 H4 headings. The page includes 102 images. 2 images (2%) 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 98% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 148 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 5 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior), Schema.org structured data (WebSite), and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for inkstory.net is too long at 83 characters: "Читать мангу, манхву и маньхуа на русском бесплатно. Слив манги для вас! — InkSt...". At 83 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 154 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://inkstory.net/, preventing duplicate content issues, the page language is declared as ru, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to inkstory.net 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. The site implements Schema.org structured data with the following types: 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. The meta keywords tag contains 38 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.