bom.tokyo

We performed a comprehensive analysis of bom.tokyo on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 2666ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 39 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 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 6 technologies across 6 categories powering bom.tokyo. The detected stack includes WordPress 5.3.21, reCAPTCHA v3, StackPath, GitHub Pages, jQuery, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, bom.tokyo receives an overall trust score of 59/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, bom.tokyo receives a trust score of 59/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 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 bom.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 bom.tokyo and identified 6 distinct technologies across 6 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 5.3.21) — manages the content and page structure for bom.tokyo. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for bom.tokyo. CDN: StackPath — accelerates content delivery by caching assets at edge locations worldwide for bom.tokyo. Hosting: GitHub Pages — provides the server infrastructure for bom.tokyo. JavaScript Library: jQuery — provides utility functions and DOM manipulation for bom.tokyo. Icon Set: Font Awesome — provides additional functionality for bom.tokyo.

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

bom.tokyo resolves to the IPv4 address 118.27.125.184, 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: uns01.lolipop.jp and uns02.lolipop.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 bom.tokyo is handled by lolipop.jp with 1 MX records configured: mx01.lolipop.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 bom.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 1 active subdomains for bom.tokyo: www.bom.tokyo. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of bom.tokyo contains 190 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, 4 H3 headings, 6 H4 headings. The page includes 30 images. 15 images (50%) 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 50% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 59 internal links pointing to other pages on the same domain and 16 external links pointing to third-party websites. There are 7 external JavaScript files, 8 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 website has social media presence across 4 platforms: Facebook (@TheBattleOfMuayThai), Twitter (@bom_muaythai), Instagram (@bom_muaythai), and Youtube (@UCBQJ4pX5KkLhW25pr8HOmlw). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for bom.tokyo is well-optimized at 46 characters: "【BOM】（ボム）-The Battle Of MuayThai-ムエタイ・キックボクシング". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 54 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. A favicon is configured. No Open Graph tags are configured. When someone shares a link to bom.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 【BOM】（ボム）-The Battle Of MuayThai-ムエタイ・キックボクシング. 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.