bebery.jp

We performed a comprehensive analysis of bebery.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 21527ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 278 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 7 technologies across 7 categories powering bebery.jp. The detected stack includes WordPress, Google Analytics 4, Google Tag Manager, Meta Pixel, GitHub Pages, Adobe Fonts, and jQuery 1.8.3.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, bebery.jp receives an overall trust score of 61/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, bebery.jp 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 quarantine 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, 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 bebery.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 bebery.jp and identified 7 distinct technologies across 7 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 bebery.jp. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for bebery.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for bebery.jp. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for bebery.jp. Hosting: GitHub Pages — provides the server infrastructure for bebery.jp. Fonts: Adobe Fonts — delivers web fonts for typography for bebery.jp. JavaScript Library: jQuery (version 1.8.3.) — provides utility functions and DOM manipulation for bebery.jp. We also extracted the following tracking identifiers: Google Tag Manager container GTM-TPC9PC2 and Meta (Facebook) Pixel ID 148194953734354. These IDs can be used to identify other websites operated by the same organization.

bebery.jp delivers its homepage in 21527ms (server response time), which is considered slow by industry standards. The total page weight is 278 KB, and we detected 1032 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 60.0% 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 7 out of 27 JavaScript files are minified. Minifying the remaining 28 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 bebery.jp produces approximately 0.14g 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 278 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for bebery.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.

bebery.jp resolves to the IPv4 address 153.142.31.204, 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 4 name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, and ns-cloud-e4.googledomains.com. 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 bebery.jp is handled by piary.jp with 1 MX records configured: mlp.piary.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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 bebery.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 bebery.jp: ftp.bebery.jp, mail.bebery.jp, webmail.bebery.jp, and www.bebery.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of bebery.jp contains 791 words of visible text content. This is a moderate amount of content. The page is structured with 17 H2 headings, 9 H3 headings, 0 H4 headings. The page includes 301 images. 21 images (7%) 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 93% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 348 internal links pointing to other pages on the same domain and 21 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 27 external JavaScript files, 8 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), and Schema.org structured data (Answer, FAQPage, ImageObject, Organization, Question, and WebSite). The website has social media presence across 3 platforms: Facebook (@tr), Twitter (@bebery_webshop), and Instagram (@bebery_inst). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for bebery.jp is good at 22 characters: "出産祝いの通販サイトBebery（ベベリー）". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 80 characters (well-optimized): "出産祝い・名入れギフトの通販サイトBebery。トレンド感＆おしゃれで実用的なアイテム多数！写真入りメッセージカードやべビーポスターなど他にはない無料特典付き！". 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.bebery.jp, preventing duplicate content issues, the meta robots directive is set to index,follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("出産祝いの通販サイトBebery（ベベリー）..."), 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 site implements Schema.org structured data with the following types: Answer, FAQPage, ImageObject, Organization, Question, 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. The meta keywords tag contains 20 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.