pjj186.github.io

We performed a comprehensive analysis of pjj186.github.io on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 927ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 119 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 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 6 domain(s) (Subject Alternative Names) and expires on 2026-09-02, which is 61 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 7 technologies across 6 categories powering pjj186.github.io. The detected stack includes Gatsby, React, Tailwind CSS, Webpack, Vite, Google Analytics 4, and GitHub Pages. The site uses Gatsby as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, pjj186.github.io receives an overall trust score of 64/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, pjj186.github.io receives a trust score of 64/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, and a valid SSL certificate issued by Let's Encrypt with 61 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 pjj186.github.io 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 pjj186.github.io 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. Framework: Gatsby — provides the application framework and routing for pjj186.github.io. UI Library: React — handles the user interface rendering and component management for pjj186.github.io. CSS Framework: Tailwind CSS — provides the styling and responsive layout system for pjj186.github.io. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for pjj186.github.io. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for pjj186.github.io. Hosting: GitHub Pages — provides the server infrastructure for pjj186.github.io. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-D6ELXGW7L3. These IDs can be used to identify other websites operated by the same organization.

pjj186.github.io delivers its homepage in 927ms (server response time), which is considered average by industry standards. The total page weight is 119 KB, and we detected 73 resource requests loading assets from 2 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 0 CSS files and 0 out of 4 JavaScript files are minified. Minifying the remaining 4 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 pjj186.github.io 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 119 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for pjj186.github.io. 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.

pjj186.github.io resolves to the IPv4 address 185.199.111.153 and also supports IPv6 (2606:50c0:8000::153), demonstrating modern network infrastructure readiness. The domain has 4 A record(s) configured. 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 pjj186.github.io. 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 pjj186.github.io contains 151 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, 1 H3 headings, 0 H4 headings. The page includes 16 images. 8 images (50%) 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 50% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 36 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 4 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior), Progressive Web App (PWA) manifest (enabling app-like installation), and RSS feed for content syndication. Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on pjj186.github.io: JCB and Apple Pay. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 1 platforms: Github (@pjj186). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for pjj186.github.io is good at 16 characters: "Home | Lenny.dev". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 78 characters (well-optimized): "프론트엔드 개발자 Lenny의 기술 블로그. React, TypeScript, JavaScript 등 웹 개발 관련 글과 일상을 공유합니다.". 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://pjj186.github.io, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Home..."), 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.