mealthy.me

We performed a comprehensive analysis of mealthy.me on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 13345ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 60 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-08-22, which is 50 days from now. The security headers analysis reveals a score of 85/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing X-Frame-Options, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 5 technologies across 5 categories powering mealthy.me. The detected stack includes WordPress, Google Tag Manager, reCAPTCHA v3, Google Fonts, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, mealthy.me receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, mealthy.me receives a trust score of 80/100, which places it in the "Very 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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 50 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 mealthy.me 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 mealthy.me and identified 5 distinct technologies across 5 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 mealthy.me. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for mealthy.me. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for mealthy.me. Fonts: Google Fonts — delivers web fonts for typography for mealthy.me. JavaScript Library: jQuery — provides utility functions and DOM manipulation for mealthy.me. We also extracted the following tracking identifiers: Google Tag Manager container GTM-MWXHV4V. These IDs can be used to identify other websites operated by the same organization.

mealthy.me delivers its homepage in 13345ms (server response time), which is considered slow by industry standards. The total page weight is 60 KB, and we detected 101 resource requests loading assets from 9 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 10 out of 16 JavaScript files are minified. Minifying the remaining 10 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 mealthy.me 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 60 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for mealthy.me. 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.

mealthy.me resolves to the IPv4 address 34.146.161.9, 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-1343.awsdns-39.org, ns-2034.awsdns-62.co.uk, ns-233.awsdns-29.com, and ns-556.awsdns-05.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 mealthy.me is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 mealthy.me. 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 mealthy.me contains 129 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 5 H2 headings, 8 H3 headings, 11 H4 headings. The page includes 17 images. 13 images (76%) 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 24% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 36 internal links pointing to other pages on the same domain and 11 external links pointing to third-party websites. There are 16 external JavaScript files, 5 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: RSS feed for content syndication. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for mealthy.me is too long at 80 characters: "株式会社Mealthy [メルシー] 健康保険組合向け特定保健指導・重症化予防、健康経営サポートのためのバーチャル栄養アシスタント 日常の食事だけで病気をなくす". At 80 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 233 characters (slightly long): "株式会社Mealthy（メルシー）は生活習慣病予防のための食習慣の改善をアプリを用いて指導をします。多忙で時間がない従業員の方でも簡単にできる、日常の食事の工夫による健康増進を栄養の専門家がサポートします。健康保険組合向けの特定保健指導を被...". 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://mealthy.co.jp/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to noodp,noydir, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to mealthy.me on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. 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.