epark.jp

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, epark.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, 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, 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 epark.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 epark.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. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for epark.jp. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for epark.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for epark.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-NSW8QL. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

epark.jp delivers its homepage in 12886ms (server response time), which is considered slow by industry standards. The total page weight is 121 KB, and we detected 290 resource requests loading assets from 21 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 15 CSS files and 4 out of 28 JavaScript files are minified. Minifying the remaining 39 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 epark.jp produces approximately 0.06g 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 121 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for epark.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

epark.jp resolves to the IPv4 address 3.174.111.155, 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-1170.awsdns-18.org, ns-1866.awsdns-41.co.uk, ns-65.awsdns-08.com, and ns-995.awsdns-60.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 epark.jp is handled by epark.jp with 1 MX records configured: mail.epark.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 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 epark.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 4 active subdomains for epark.jp: api.epark.jp, help.epark.jp, mail.epark.jp, and www.epark.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of epark.jp contains 210 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 3 H2 headings, 79 H3 headings, 0 H4 headings. The page includes 94 images. 1 images (1%) 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 99% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 78 internal links pointing to other pages on the same domain and 66 external links pointing to third-party websites. There are 28 external JavaScript files, 15 CSS stylesheets, and 4 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages). Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@epark.portal), Twitter (@epark_jp), and Instagram (@epark_official). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for epark.jp is good at 23 characters: "EPARK - 人気施設の予約・順番受付サイト". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 105 characters (well-optimized): "人気店順番受付・ネット予約ならEPARK(イーパーク)。飲食店・テイクアウト・歯医者・病院・リラク・エステなどをネット予約・順番受付して、店頭での待ち時間が空き時間に♪ 施設情報・口コミ・クーポンも多数掲載中！". 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://epark.jp/, preventing duplicate content issues, the page language is declared as ja, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("EPARK - 人気施設の予約・順番受付サイト..."), 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.

🤖 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 epark.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-NSW8QL.