94ferry.co.jp

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, 94ferry.co.jp receives a trust score of 59/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, 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 94ferry.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.

🤖 AI Summary

Our technology detection engine scanned 94ferry.co.jp and identified 8 distinct technologies across 7 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 (version 7.0) — manages the content and page structure for 94ferry.co.jp. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for 94ferry.co.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for 94ferry.co.jp. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for 94ferry.co.jp. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for 94ferry.co.jp. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for 94ferry.co.jp. JavaScript Library: jQuery (version 3.1.1.) — provides utility functions and DOM manipulation for 94ferry.co.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-W7H57V6 and Meta (Facebook) Pixel ID 1436529087073674. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

94ferry.co.jp delivers its homepage in 16014ms (server response time), which is considered slow by industry standards. The total page weight is 200 KB, and we detected 180 resource requests loading assets from 14 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: 2 out of 15 CSS files and 10 out of 18 JavaScript files are minified. Minifying the remaining 21 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 94ferry.co.jp produces approximately 0.1g 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 200 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 94ferry.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.

🤖 AI Summary

94ferry.co.jp resolves to the IPv4 address 153.127.185.207, 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 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 94ferry.co.jp is handled by co.jp with 1 MX records configured: 94ferry.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 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 94ferry.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. Our subdomain enumeration scan discovered 3 active subdomains for 94ferry.co.jp: ftp.94ferry.co.jp, mail.94ferry.co.jp, and www.94ferry.co.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of 94ferry.co.jp contains 110 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 0 H2 headings, 3 H3 headings, 0 H4 headings. The page includes 18 images. 7 images (39%) 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 61% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 54 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. There are 18 external JavaScript files, 15 CSS stylesheets, and 2 iframes on the page. The site implements the following web standards and features: Schema.org structured data (Article, ImageObject, Organization, Person, SearchAction, WebPage, and WebSite) and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@tr), Twitter (@orange_ferry), and Instagram (@p). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for 94ferry.co.jp is good at 23 characters: "オレンジフェリー | 四国開発フェリー株式会社". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 165 characters (slightly long): "オレンジフェリーで行く豪華な船旅。大阪南港・神戸から四国愛媛の東予・新居浜へ。松山道後温泉にも便利！20時より乗船し、船内でご入浴・お食事ができますので、ごゆっくりおくつろぎ下さい。四国オレンジフェリーは、四国（東予・新居浜）と関西（大阪・...". 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://www.orange-ferry.co.jp, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("オレンジフェリー | 四国開発フェリー株式会社..."), OG description, 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. The site implements Schema.org structured data with the following types: Article, ImageObject, Organization, Person, SearchAction, WebPage, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.

🤖 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 94ferry.co.jp. 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-W7H57V6, meta_pixel_id: 1436529087073674.