raysee.jp

We performed a comprehensive analysis of raysee.jp on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 29815ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 1897 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 1 domain(s) (Subject Alternative Names) and expires on 2026-09-22, which is 80 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 6 technologies across 5 categories powering raysee.jp. The detected stack includes WordPress, Next.js css, Webpack, Microsoft Clarity, Meta Pixel, and Twitter Pixel. The site uses Next.js as its primary framework (version css). Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, raysee.jp receives an overall trust score of 70/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, raysee.jp receives a trust score of 70/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, a valid SSL certificate issued by Let's Encrypt with 80 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. 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 raysee.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 raysee.jp and identified 6 distinct technologies across 5 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 raysee.jp. Framework: Next.js (version css) — provides the application framework and routing for raysee.jp. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for raysee.jp. Analytics: Microsoft Clarity — tracks visitor behavior and provides traffic insights for raysee.jp. Advertising: Meta Pixel and Twitter Pixel — handles advertising pixel tracking and conversion measurement for raysee.jp. We also extracted the following tracking identifiers: Meta (Facebook) Pixel ID 1770030607134322. These IDs can be used to identify other websites operated by the same organization.

raysee.jp delivers its homepage in 29815ms (server response time), which is considered slow by industry standards. The total page weight is 1897 KB, and we detected 774 resource requests loading assets from 4 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 11 JavaScript files are minified. Minifying the remaining 12 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 raysee.jp produces approximately 0.93g of CO₂, earning a carbon rating of F. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 1897 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for raysee.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.

raysee.jp resolves to the IPv4 address 76.76.21.21, 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 4 name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com. Having 4 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 raysee.jp is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 raysee.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 raysee.jp contains 1,976 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 15 H2 headings, 5 H3 headings, 0 H4 headings. The page includes 655 images. 265 images (40%) 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 60% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 96 internal links pointing to other pages on the same domain and 3 external links pointing to third-party websites. There are 11 external JavaScript files, 1 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 Progressive Web App (PWA) manifest (enabling app-like installation). 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 raysee.jp: Visa, Mastercard, JCB, and Diners Club. 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: Facebook (@tr). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for raysee.jp is well-optimized at 35 characters: "チャット占い | RAYSEE(レイシー) 【初回無料で当たると話題】". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 60 characters (acceptable): "完全非公開で恋愛、結婚、相性、片思い、復縁などの日々の不安や悩みを相談できます。実力派の占い師があなたの未来を徹底鑑定！". 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, 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 ("チャット占い | RAYSEE(レイシー) 【初回無料で当たると話題】..."), 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.