angelic-angel.blog

We performed a comprehensive analysis of angelic-angel.blog on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 37533ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 577 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-19, which is 48 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 14 technologies across 10 categories powering angelic-angel.blog. The detected stack includes WordPress, Drupal, Magento, Angular, Remix, React, Google Analytics 4, Google Ads, Google AdSense, Cloudflare, StackPath, Google Fonts, jQuery, and Font Awesome. The primary e-commerce platform is Magento. The site uses Angular 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, angelic-angel.blog receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, angelic-angel.blog 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 Google Trust Services with 48 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 angelic-angel.blog 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 angelic-angel.blog and identified 14 distinct technologies across 10 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 and Drupal — manages the content and page structure for angelic-angel.blog. Ecommerce: Magento — powers the online store and shopping functionality for angelic-angel.blog. Framework: Angular and Remix — provides the application framework and routing for angelic-angel.blog. UI Library: React — handles the user interface rendering and component management for angelic-angel.blog. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for angelic-angel.blog. Advertising: Google Ads and Google AdSense — handles advertising pixel tracking and conversion measurement for angelic-angel.blog. CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for angelic-angel.blog. Fonts: Google Fonts — delivers web fonts for typography for angelic-angel.blog. JavaScript Library: jQuery — provides utility functions and DOM manipulation for angelic-angel.blog. Icon Set: Font Awesome — provides additional functionality for angelic-angel.blog. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-LYED7RZRS2. These IDs can be used to identify other websites operated by the same organization.

angelic-angel.blog delivers its homepage in 37533ms (server response time), which is considered slow by industry standards. The total page weight is 577 KB, and we detected 112 resource requests loading assets from 26 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 3 out of 5 JavaScript files are minified. Minifying the remaining 2 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 angelic-angel.blog produces approximately 0.28g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 577 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for angelic-angel.blog. 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.

angelic-angel.blog resolves to the IPv4 address 172.67.136.140 and also supports IPv6 (2606:4700:3036::6815:5e8c), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: lewis.ns.cloudflare.com and princess.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 angelic-angel.blog. 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 angelic-angel.blog contains 175 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 10 H2 headings, 8 H3 headings, 0 H4 headings. The page includes 21 images. 21 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 48 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 5 external JavaScript files, 0 CSS stylesheets, and 0 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. We detected the following payment methods accepted on angelic-angel.blog: Visa, Mastercard, American Express, Discover, Alipay, JCB, Diners Club, and Apple Pay. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for angelic-angel.blog is good at 28 characters: "エンジェルナンバー｜恋愛・復縁・ツインレイ・ツインソウル". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 118 characters (well-optimized): "エンジェルナンバーで恋愛・復縁・ツインレイのことがわかります。数字にはそれぞれ意味や波動があり、何度も目にする数字はただの偶然ではありません。Angelic Angelでは天使が届けてくれる数字のメッセージをわかりやすく解説しています。". 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 /, preventing duplicate content issues, the page language is declared as ja, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Angelic Angel Blog..."), 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.