3bre.jp

We performed a comprehensive analysis of 3bre.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 23687ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 116 KB, and the site is served behind a CDN (Content Delivery Network). 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 65/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Strict-Transport-Security (HSTS) 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 2 technologies across 2 categories powering 3bre.jp. The detected stack includes Akamai and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 3bre.jp receives an overall trust score of 69/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, 3bre.jp receives a trust score of 69/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 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 3bre.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 3bre.jp and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CDN: Akamai — accelerates content delivery by caching assets at edge locations worldwide for 3bre.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for 3bre.jp.

3bre.jp delivers its homepage in 23687ms (server response time), which is considered slow by industry standards. The total page weight is 116 KB, and we detected 446 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: 1 out of 5 CSS files and 4 out of 8 JavaScript files are minified. Minifying the remaining 8 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 3bre.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 116 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 3bre.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.

3bre.jp resolves to the IPv4 address 3.173.254.16, 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 4 A record(s) configured. The domain name system is managed by 2 name servers: ns.makeshop.jp and ns2.makeshop.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 3bre.jp is handled by makeshop.jp with 1 MX records configured: mail4.makeshop.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 3bre.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 2 active subdomains for 3bre.jp: mail.3bre.jp and www.3bre.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of 3bre.jp contains 700 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 3 H3 headings, 1 H4 headings. The page includes 82 images. 12 images (15%) 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 85% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 353 internal links pointing to other pages on the same domain and 0 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 8 external JavaScript files, 5 CSS stylesheets, and 0 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 title tag for 3bre.jp is well-optimized at 54 characters: "「3bre」 ティグルブロカンテ、henderscheme、yarmo、PRAS、RoToTo　正規取扱い店". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 145 characters (well-optimized): "3ble（サブレ）は、福岡のメンズ、レディースのアパレルブランド、tigrebrocante（ティグルブロカンテ）やHenderScheme、PRAS、TROENTORP、ROTOTO、TID Watches、FERNAND LEATHER...". 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. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("「3bre」 ティグルブロカンテ、henderscheme、yarmo、PRAS、RoToTo　正規取扱い店..."), OG description, 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 with Large Image is configured, which controls how links appear when shared on Twitter/X. The "Summary with Large Image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.