clocall.jp

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, clocall.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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. 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 clocall.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 clocall.jp and identified 5 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 (version 6.0.2) — manages the content and page structure for clocall.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for clocall.jp. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for clocall.jp. Video: YouTube Embed — provides video hosting and playback for clocall.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for clocall.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-KD87ZXW. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

clocall.jp delivers its homepage in 11259ms (server response time), which is considered slow by industry standards. The total page weight is 72 KB, and we detected 277 resource requests loading assets from 13 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 5 CSS files and 6 out of 13 JavaScript files are minified. Minifying the remaining 10 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 clocall.jp produces approximately 0.04g 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 72 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for clocall.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

clocall.jp resolves to the IPv4 address 104.26.1.196 and also supports IPv6 (2606:4700:20::ac43:4bd3), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: emily.ns.cloudflare.com and will.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. Email for clocall.jp is handled by Microsoft 365 with 1 MX records configured: clocall-jp.mail.protection.outlook.com. 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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for clocall.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 clocall.jp: admin.clocall.jp, api.clocall.jp, and www.clocall.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of clocall.jp contains 166 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, 0 H3 headings, 0 H4 headings. The page includes 113 images. 82 images (73%) 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 27% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 119 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 13 external JavaScript files, 5 CSS stylesheets, and 3 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 (BreadcrumbList, CollectionPage, EntryPoint, ListItem, Organization, SearchAction, WebPage, and WebSite).

🤖 AI Summary

The title tag for clocall.jp is well-optimized at 35 characters: "クラコール | 信頼されるクラウド通信サービスを簡単に。はじめやすく。". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 27 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 https://clocall.jp/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("クラコール | 信頼されるクラウド通信サービスを簡単に。はじめやすく。..."), 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: BreadcrumbList, CollectionPage, EntryPoint, ListItem, Organization, 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 clocall.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-KD87ZXW.