bridal-bloom.jp

We performed a comprehensive analysis of bridal-bloom.jp on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 36017ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 11.2% size reduction. The total page weight is 62 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by GlobalSign nv-sa (OV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2027-02-17, which is 233 days from now. 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 3 technologies across 3 categories powering bridal-bloom.jp. The detected stack includes Google Analytics 4, Google Tag Manager, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, bridal-bloom.jp receives an overall trust score of 73/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, bridal-bloom.jp receives a trust score of 73/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, a valid SSL certificate issued by GlobalSign nv-sa with 233 days until expiration, and SPF (Sender Policy Framework) email authentication preventing email spoofing. 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 bridal-bloom.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 bridal-bloom.jp and identified 3 distinct technologies across 3 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 bridal-bloom.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for bridal-bloom.jp. JavaScript Library: jQuery — provides utility functions and DOM manipulation for bridal-bloom.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-CYZHT7LWV1 and Google Tag Manager container GTM-WJ2MW3B. These IDs can be used to identify other websites operated by the same organization.

bridal-bloom.jp delivers its homepage in 36017ms (server response time), which is considered slow by industry standards. The total page weight is 62 KB, and we detected 147 resource requests loading assets from 14 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 11.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 5 CSS files and 1 out of 5 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. 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 bridal-bloom.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 62 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for bridal-bloom.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.

bridal-bloom.jp resolves to the IPv4 address 3.164.110.111, 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 bridal-bloom.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 is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 bridal-bloom.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.

The homepage of bridal-bloom.jp contains 170 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 10 H2 headings, 14 H3 headings, 1 H4 headings, 1 H5, and 0 H6 headings. The page includes 62 images. 1 images (2%) 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 98% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 2 internal links pointing to other pages on the same domain and 66 external links pointing to third-party websites. There are 5 external JavaScript files, 5 CSS stylesheets, and 4 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on bridal-bloom.jp: Visa, American Express, JCB, and Diners Club. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for bridal-bloom.jp is well-optimized at 35 characters: "ブライダルインナーの専門サイト｜【整形3Dインナー】ブライダルブルーム". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 170 characters (slightly long): "ブライダルインナーの専門店ブライダルブルーム（bridalbloom）は、脇肉を解消しカップ上辺の浮きを軽減する、特許3Dフィットワイヤーの下着で、毎年8万人以上の花嫁様に愛用される人気のウエディングドレス用インナーの日本製ブランドです。補...". 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.bridal-bloom.jp/, preventing duplicate content issues. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("ブライダルインナーの専門サイト｜【整形3Dインナー】bridalbloom..."), 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. The meta keywords tag contains 10 terms including ブライダルインナー, 結婚式用下着, 結婚式用インナー, ウェディングドレス用インナー, and ドレス用下着. 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.