royalfortune.co.jp

We performed a comprehensive analysis of royalfortune.co.jp on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 5740ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 19 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_256_GCM_SHA384 cipher suite and ECDSA-SHA384 signature algorithm. The certificate covers 18 domain(s) (Subject Alternative Names) and expires on 2026-09-13, which is 71 days from now. The security headers analysis reveals a score of 80/100 (good). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Content-Security-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 1 technologies across 1 categories powering royalfortune.co.jp. The detected stack includes Google Analytics 4. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, royalfortune.co.jp receives an overall trust score of 82/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, royalfortune.co.jp receives a trust score of 82/100, which places it in the "Very 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 Let's Encrypt with 71 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a reject policy — the strongest available setting. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 royalfortune.co.jp 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 royalfortune.co.jp and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for royalfortune.co.jp.

royalfortune.co.jp delivers its homepage in 5740ms (server response time), which is considered slow by industry standards. The total page weight is 19 KB, and we detected 84 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 4 CSS files and 1 out of 4 JavaScript files are minified. Minifying the remaining 7 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 royalfortune.co.jp produces approximately 0.01g 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 19 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for royalfortune.co.jp. 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.

royalfortune.co.jp resolves to the IPv4 address 133.242.183.7 and also supports IPv6 (2401:2500:102:1b02:133:242:183:7), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: ns1.dns.ne.jp and ns2.dns.ne.jp. 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 royalfortune.co.jp is handled by co.jp with 1 MX records configured: royalfortune.co.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 not enabled for royalfortune.co.jp. 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 royalfortune.co.jp contains 197 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 1 H2 headings, 6 H3 headings, 0 H4 headings. The page includes 17 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 39 internal links pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 4 external JavaScript files, 4 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 title tag for royalfortune.co.jp is good at 17 characters: "株式会社Royal Forutne". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 87 characters (well-optimized): "株式会社 Royal Fortuneは、占いコンテンツの作成事業、鑑定用プログラムの作成事業、占い館の運営事業、鑑定業務全般や鑑定士養成事業などの占い事業を展開する会社です。". 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 page language is declared as ja. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("株式会社Royal Forutne..."), 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. The meta keywords tag contains 10 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.