act2.tokyo

We performed a comprehensive analysis of act2.tokyo on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 55448ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 13 KB. Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 15/100 (poor). The following security headers are properly configured: X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-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 1 technologies across 1 categories powering act2.tokyo. The detected stack includes Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, act2.tokyo receives an overall trust score of 58/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, act2.tokyo receives a trust score of 58/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 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 act2.tokyo 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 act2.tokyo and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Fonts: Google Fonts — delivers web fonts for typography for act2.tokyo.

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

act2.tokyo resolves to the IPv4 address 157.120.209.58, 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: ns-rs1.gmoserver.jp and ns-rs2.gmoserver.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 act2.tokyo is handled by ne.jp with 1 MX records configured: mail1002.onamae.ne.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 (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 act2.tokyo. 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 2 active subdomains for act2.tokyo: mail.act2.tokyo and www.act2.tokyo. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of act2.tokyo contains 75 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 2 H2 headings, 2 H3 headings, 3 H4 headings. The page includes 12 images. 2 images (17%) 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 83% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 19 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 2 external JavaScript files, 5 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for act2.tokyo is well-optimized at 35 characters: "Act 2 - Learning Through Experience". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for act2.tokyo. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as ja. No Open Graph tags are configured. When someone shares a link to act2.tokyo on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The meta keywords tag contains 1 terms including フォーラムシアター研修 ロールプレイ研修 コミュニケーション研修実践 インタラクティブ研修 １on1面談　フィードバック研修　ハラスメント防止　コンプライアンス体験型研修 ダイバーシティ＆インクルージョン 　DEI研修　リーダシップ研修 チームビルディング 参加型研修 飽きない 社員研修 行動変容研修 対話型ワークショップ 営業ロールプレイ 対話力研修 接客ロールプレイ研修 企業研修 社員研修 人材育成 組織開発 事担当者向け. 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.