2ji.pink Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of 2ji.pink on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 6898ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 221 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 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 3 technologies across 3 categories powering 2ji.pink. The detected stack includes WordPress, Google Tag Manager, and jQuery.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 2ji.pink receives an overall trust score of 53/100, classified as "Caution Advised".
HTTP Response
Status200 OK
Response Time6898ms
ProtocolHTTP/2
Page Size221 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests411
3rd Party Domains48
RedirectNone
Detected Technologies (3)
• WordPress
🏷️ Google Tag Manager
📦 jQuery
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=2ji.pink
Type—
TLS VersionTLS 1.2
Cipher SuiteECDHE-ECDSA-CHACHA20-POLY1305
Algorithm—
Issued—
Expires— (? days)
SANs—
2ji.pink Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, 2ji.pink receives a trust score of 53/100, which places it in the "Caution Advised" 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.
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 2ji.pink 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.
Trust Signals
✅ Valid HTTPS
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
2ji.pink Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned 2ji.pink and identified 3 distinct technologies across 3 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 2ji.pink.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for 2ji.pink.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for 2ji.pink.
We also extracted the following tracking identifiers: Google Tag Manager container GTM-TMX6PTV. These IDs can be used to identify other websites operated by the same organization.
CMS
Tag Manager
🏷️ Google Tag Manager(95%)
JavaScript Library
Tracking IDs
2ji.pink Performance, Speed & Core Web Vitals
🤖 AI Summary
2ji.pink delivers its homepage in 6898ms (server response time), which is considered slow by industry standards. The total page weight is 221 KB, and we detected 411 resource requests loading assets from 48 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: 4 out of 8 CSS files and 8 out of 19 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 2ji.pink produces approximately 0.11g 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 221 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 2ji.pink. 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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.11g
RatingA
Page Weight & Optimization
HTML Size221 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests411
3rd Party Domains48
CSS Minified4/8
JS Minified8/19
2ji.pink DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
2ji.pink resolves to the IPv4 address 104.21.57.24 and also supports IPv6 (2606:4700:3032::ac43:9e66), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured.
The domain name system is managed by 2 name servers: nick.ns.cloudflare.com and robin.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 2ji.pink is handled by 2ji.pink with 1 MX records configured: _dc-mx.8849f2374bef.2ji.pink. 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 2ji.pink. 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 2ji.pink: www.2ji.pink. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
104.21.57.24
172.67.158.102
AAAA
2606:4700:3032::ac43:9e66
NS
nick.ns.cloudflare.com
robin.ns.cloudflare.com
MX
_dc-mx.8849f2374bef.2ji.pink
Email & Authentication
MX Provider2ji.pink
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportYes ✓
Subdomains (1 found)
2ji.pink Page Content, Images & Accessibility
🤖 AI Summary
The homepage of 2ji.pink contains 421 words of visible text content. This is a moderate amount of content. The page is structured with 21 H2 headings, 3 H3 headings, 4 H4 headings.
The page includes 97 images. 21 images (22%) 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 78% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 127 internal links pointing to other pages on the same domain and 96 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 19 external JavaScript files, 8 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), Progressive Web App (PWA) manifest (enabling app-like installation), and RSS feed for content syndication.
Notable missing features: robots.txt 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 (@2jilog_pink) and Pinterest (@pin). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1二次ろぐぴんく
H2 Tags21
H3 Tags3
H4 Tags4
H5 Tags0
H6 Tags0
Internal Links127
External Links96
Assets & Features
JavaScript Files19
JS Minified8/19
CSS Files8
CSS Minified4/8
Iframes1
Images97
Missing Alt21
SitemapYes ✓
Robots.txtNo
PWAYes ✓
AMPNo
RSS FeedYes ✓
Social Media Presence
Twitter: @2jilog_pinkPinterest: @pin
2ji.pink SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for 2ji.pink is well-optimized at 55 characters: "二次ろぐぴんく | 二次ロリ画像・二次貧乳微乳画像・二次美少女画像など二次エロ画像やGIFアニメのまとめサイト". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
The meta description is 189 characters (slightly long): "二次ロリ画像を中心に欲望全開で二次元のロリや萌えなエロ画像をまとめた、画像まとめサイトです。二次ろぐぴんくはちょっと管理人の趣味に偏ったまとめが多いです。ロリ少女に魅力を感じるけど、三次ロリ少女にひどい目にあってほしくない…そんな紳士の方た...". 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://2ji.pink/, 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 ("二次ろぐぴんく | 二次ロリ画像・二次貧乳微乳画像・二次美少女画像など二次エロ画像やGIFアニメのまとめサイト..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.
Google SERP Preview
二次ろぐぴんく | 二次ロリ画像・二次貧乳微乳画像・二次美少女画像など二次エロ画像やGIFアニメのまとめサイト
https://2ji.pink
二次ロリ画像を中心に欲望全開で二次元のロリや萌えなエロ画像をまとめた、画像まとめサイトです。二次ろぐぴんくはちょっと管理人の趣味に偏ったまとめが多いです。ロリ少女に魅力を感じるけど、三次ロリ少女にひどい目にあってほしくない…そんな紳士の方たちの憩いの場になればと思っています。二次ロリ系や百合レズ系、オナニー系やロリ系など偏ったジャンルが大好きなので、苦手な方はお察しください。
Meta Tags
Title二次ろぐぴんく | 二次ロリ画像・二次貧乳微乳画像・二次美少女画像など二次エロ画像やGIFアニメのまとめサイト...
Title Length55 chars
Meta Desc Length189 chars
H1二次ろぐぴんく
Languageja
Canonicalhttps://2ji.pink/
Meta Robotsmax-image-preview:large
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageSet ✓
Twitter Cardsummary
FaviconSet ✓
Open Graph Preview
2ji.pink
二次ろぐぴんく | 二次ロリ画像・二次貧乳微乳画像・二次美少女画像など二次エロ画像やGIFアニメのまとめサイト
二次ロリ画像を中心に欲望全開で二次元のロリや萌えなエロ画像をまとめた、画像まとめサイトです。二次ろぐぴんくはちょっと管理人の趣味に偏ったまとめが多いです。ロリ少女に魅力を感じるけど、三次ロリ少女にひどい目にあってほしくない…そんな紳士の方たちの憩いの場になればと思っています。二次ロリ系や百合レズ系、オナニー系やロリ系な
2ji.pink Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with 2ji.pink. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: gtm_id: GTM-TMX6PTV.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)