workers-accident.jp

We performed a comprehensive analysis of workers-accident.jp on 2026-07-05. The website returned an HTTP 200 status code with a server response time of 10490ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 85 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 sha256WithRSAEncryption signature algorithm. The certificate covers 3 domain(s) (Subject Alternative Names) and expires on 2026-09-24, which is 81 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 4 technologies across 4 categories powering workers-accident.jp. The detected stack includes WordPress, Google Analytics 4, Google Tag Manager, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, workers-accident.jp receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, workers-accident.jp receives a trust score of 66/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 Let's Encrypt with 81 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 workers-accident.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 workers-accident.jp and identified 4 distinct technologies across 4 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 workers-accident.jp. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for workers-accident.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for workers-accident.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for workers-accident.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-KBS4V32. These IDs can be used to identify other websites operated by the same organization.

workers-accident.jp delivers its homepage in 10490ms (server response time), which is considered slow by industry standards. The total page weight is 85 KB, and we detected 183 resource requests loading assets from 7 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: 1 out of 3 CSS files and 2 out of 5 JavaScript files are minified. Minifying the remaining 5 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 workers-accident.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 85 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for workers-accident.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.

workers-accident.jp resolves to the IPv4 address 157.7.44.177, 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: dns0.heteml.jp and dns1.heteml.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 workers-accident.jp is handled by hetemail.jp with 1 MX records configured: mx.hetemail.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 workers-accident.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 workers-accident.jp contains 430 words of visible text content. This is a moderate amount of content. The page is structured with 24 H2 headings, 14 H3 headings, 0 H4 headings. The page includes 44 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 107 internal links pointing to other pages on the same domain and 18 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 5 external JavaScript files, 3 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and Schema.org structured data (BreadcrumbList, CollectionPage, EntryPoint, ListItem, PropertyValueSpecification, SearchAction, and WebSite). Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for workers-accident.jp is well-optimized at 37 characters: "【労働災害（労災）被害専門の弁護士による無料相談】弁護士法人小杉法律事務所". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 118 characters (well-optimized): "弁護士法人小杉法律事務所は労災被害専門の弁護士事務所です。労災を専門的に扱い、弁護士資格のみならず社労士資格を有するプロが対応します。労基署への休業給付や後遺障害の申請、会社に対する損害賠償請求が強いです。無料相談｜全国対応｜着手金無料". 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://workers-accident.jp/, preventing duplicate content issues, the page language is declared as ja, and the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1. 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: BreadcrumbList, CollectionPage, EntryPoint, ListItem, PropertyValueSpecification, 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.