mbok.jp

We performed a comprehensive analysis of mbok.jp on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 10140ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 5.2% size reduction. The total page weight is 64 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 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 7 technologies across 6 categories powering mbok.jp. The detected stack includes Google Analytics 4, Google Tag Manager, Meta Pixel, Google Ads, Zendesk, Cloudflare, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, mbok.jp receives an overall trust score of 64/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, mbok.jp receives a trust score of 64/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, 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, 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 mbok.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 mbok.jp and identified 7 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. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for mbok.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for mbok.jp. Advertising: Meta Pixel and Google Ads — handles advertising pixel tracking and conversion measurement for mbok.jp. Support: Zendesk — handles customer support tickets and knowledge bases for mbok.jp. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for mbok.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for mbok.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-L8FMB16Q20, Google Tag Manager container GTM-MBM7N9S2, and Meta (Facebook) Pixel ID 343968731494495. These IDs can be used to identify other websites operated by the same organization.

mbok.jp delivers its homepage in 10140ms (server response time), which is considered slow by industry standards. The total page weight is 64 KB, and we detected 266 resource requests loading assets from 19 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 5.2% 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 8 CSS files and 8 out of 24 JavaScript files are minified. Minifying the remaining 24 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 mbok.jp produces approximately 0.03g 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 64 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for mbok.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.

mbok.jp resolves to the IPv4 address 13.193.198.243, 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 3 A record(s) configured. The domain name system is managed by 4 name servers: ns-1138.awsdns-14.org, ns-1867.awsdns-41.co.uk, ns-491.awsdns-61.com, and ns-791.awsdns-34.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 mbok.jp is handled by amazonaws.com with 1 MX records configured: inbound-smtp.us-east-1.amazonaws.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 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 mbok.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 mbok.jp: api.mbok.jp, dev.mbok.jp, m.mbok.jp, and www.mbok.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of mbok.jp contains 281 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 6 H2 headings, 10 H3 headings, 0 H4 headings. The page includes 45 images. 19 images (42%) 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 58% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 167 internal links pointing to other pages on the same domain and 13 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 24 external JavaScript files, 8 CSS stylesheets, and 2 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 2 platforms: Facebook (@tr) and Twitter (@mbok_jp). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for mbok.jp is good at 29 characters: "オークション モバオク - お得な新品・中古品を買うなら！". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 118 characters (well-optimized): "オークション モバオクは新品・中古品などの人気のブランドアイテムや自動車、バイクが続々出品中！誰でも超カンタンに出品・入札・落札が楽しめる、日本最大級のオークションサイトです。スマホ・アプリ・PC・ケータイ・タブレット、それぞれに対応。". 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://www.mbok.jp/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to index,follow,noodp, 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 (article). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.