5291ban.com

We performed a comprehensive analysis of 5291ban.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 40768ms. 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. 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-Frame-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 5291ban.com. The detected stack includes WordPress, WooCommerce, reCAPTCHA v3, Google Fonts, jQuery, and Font Awesome. The primary e-commerce platform is WooCommerce. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 5291ban.com receives an overall trust score of 61/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, 5291ban.com receives a trust score of 61/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 none 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 5291ban.com 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 5291ban.com 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 — manages the content and page structure for 5291ban.com. Ecommerce: WooCommerce — powers the online store and shopping functionality for 5291ban.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for 5291ban.com. Fonts: Google Fonts — delivers web fonts for typography for 5291ban.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for 5291ban.com. Icon Set: Font Awesome — provides additional functionality for 5291ban.com.

5291ban.com delivers its homepage in 40768ms (server response time), which is considered slow by industry standards. The total page weight is 85 KB, and we detected 190 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: 4 out of 9 CSS files and 6 out of 15 JavaScript files are minified. Minifying the remaining 14 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 5291ban.com 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 5291ban.com. 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.

5291ban.com resolves to the IPv4 address 95.217.149.230, 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: dns1.stationet.com and dns2.stationet.com. 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 5291ban.com is handled by mxrouting.net with 2 MX records configured: moose.mxrouting.net and moose-relay.mxrouting.net. 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 (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 5291ban.com. 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 5291ban.com: shop.5291ban.com and www.5291ban.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of 5291ban.com contains 180 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 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 33 images. 32 images (97%) 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 3% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 111 internal links pointing to other pages on the same domain and 9 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 15 external JavaScript files, 9 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior), Schema.org structured data (BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, ReadAction, SearchAction, WebPage, and WebSite), and RSS feed for content syndication. Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@profile.php), Twitter (@5291ban), and Instagram (@miyamoto5291ban). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for 5291ban.com is too long at 77 characters: "ごふくいちばん 黒門 みやもと - 大阪 黒門市場 呉服 着物 きもの 大衆演劇 舞台衣装 きものクリーニング 振袖 お宮参り 初着 着付け教室 おみやげ". At 77 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 70 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://www.5291ban.com/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to max-snippet:-1,max-image-preview:standard,max-video-preview:-1, 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 (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, EntryPoint, ImageObject, ListItem, Organization, ReadAction, SearchAction, WebPage, 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.