suijobus.co.jp

We performed a comprehensive analysis of suijobus.co.jp on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 19864ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 95 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Sectigo Limited (OV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES256-GCM-SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-07-17, which is 10 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, 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 3 technologies across 3 categories powering suijobus.co.jp. The detected stack includes WordPress, Vite, and Google Analytics 4. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, suijobus.co.jp receives an overall trust score of 61/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, suijobus.co.jp receives a trust score of 61/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, a valid SSL certificate issued by Sectigo Limited with 10 days until expiration, and SPF (Sender Policy Framework) email authentication preventing email spoofing. 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 suijobus.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 suijobus.co.jp and identified 3 distinct technologies across 3 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 suijobus.co.jp. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for suijobus.co.jp. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for suijobus.co.jp.

suijobus.co.jp delivers its homepage in 19864ms (server response time), which is considered slow by industry standards. The total page weight is 95 KB, and we detected 138 resource requests loading assets from 8 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. No compression is currently enabled on suijobus.co.jp. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 1 CSS files and 1 out of 8 JavaScript files are minified. Minifying the remaining 8 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 suijobus.co.jp produces approximately 0.05g 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 95 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for suijobus.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.

suijobus.co.jp resolves to the IPv4 address 103.217.137.158, 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-1495.awsdns-58.org, ns-1965.awsdns-53.co.uk, ns-502.awsdns-62.com, and ns-521.awsdns-01.net. 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 suijobus.co.jp is handled by co.jp with 1 MX records configured: suijobus.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 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 suijobus.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 suijobus.co.jp contains 435 words of visible text content. This is a moderate amount of content. The page is structured with 7 H2 headings, 17 H3 headings, 2 H4 headings. The page includes 15 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 100 internal links pointing to other pages on the same domain and 10 external links pointing to third-party websites. There are 8 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 Schema.org structured data (SearchAction and WebSite). The website has social media presence across 2 platforms: Instagram (@tokyocruiseship) and Youtube (@UCB3YP-077UTLn2fV0ExTS1Q). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for suijobus.co.jp is well-optimized at 40 characters: "水上バス・東京湾クルーズ | 【公式】東京都観光汽船（TOKYO CRUISE）". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 117 characters (well-optimized): "水上バスでの隅田川や東京湾での優雅なクルージングが楽しめます。チャーター・貸切クルーズ、初日の出やお花見船、隅田川花火大会、クリスマスクルーズなどのイベントクルーズなど、いつもとは違う確度から360°東京の景色を堪能することが出来ます". 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.suijobus.co.jp/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to noodp, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("東京都観光汽船（TOKYO CRUISE）..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" 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: SearchAction 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. The meta keywords tag contains 22 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.