imayaburger.com

We performed a comprehensive analysis of imayaburger.com on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 7085ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 513 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 2 domain(s) (Subject Alternative Names) and expires on 2026-08-07, which is 38 days from now. 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 6 categories powering imayaburger.com. The detected stack includes WordPress 6.1.6, Webpack, Google Analytics 4, Google Fonts, Adobe Fonts, jQuery, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, imayaburger.com receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, imayaburger.com receives a trust score of 60/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 and a valid SSL certificate issued by Let's Encrypt with 38 days until expiration. 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 imayaburger.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 imayaburger.com and identified 7 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 (version 6.1.6) — manages the content and page structure for imayaburger.com. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for imayaburger.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for imayaburger.com. Fonts: Google Fonts and Adobe Fonts — delivers web fonts for typography for imayaburger.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for imayaburger.com. Icon Set: Font Awesome — provides additional functionality for imayaburger.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-0GTCNV4F95. These IDs can be used to identify other websites operated by the same organization.

imayaburger.com delivers its homepage in 7085ms (server response time), which is considered slow by industry standards. The total page weight is 513 KB, and we detected 151 resource requests loading assets from 19 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 13 CSS files and 10 out of 15 JavaScript files are minified. Minifying the remaining 18 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 imayaburger.com produces approximately 0.25g of CO₂, earning a carbon rating of B. 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 513 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for imayaburger.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.

imayaburger.com resolves to the IPv4 address 118.27.125.226, 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: dns01.muumuu-domain.com and dns02.muumuu-domain.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 imayaburger.com is handled by lolipop.jp with 1 MX records configured: mx01.lolipop.jp. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. 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 imayaburger.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.

The homepage of imayaburger.com contains 162 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 3 H2 headings, 31 H3 headings, 0 H4 headings. The page includes 43 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 7 internal links pointing to other pages on the same domain and 30 external links pointing to third-party websites. There are 15 external JavaScript files, 13 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, ContactPoint, EntryPoint, ImageObject, ListItem, Organization, 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 (@imayaburger), Twitter (@imayaburger), and Instagram (@p). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for imayaburger.com is good at 17 characters: "【閉店】今屋のハンバーガー 西新店". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 146 characters (well-optimized): "西公園で創業40余年、福岡市を代表するソウルフード「今屋のハンバーガー」が西新（高取）にオープンしました。本店と変わらぬ味をお楽しみ下さい。●営業時間：11:00～21:30 ●定休日：水曜日 ●電話：092-836-8364 ●住所：〒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://imayaburger.com/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to noindex, nofollow, max-image-preview:large, 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 (article). 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" 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, ContactPoint, EntryPoint, ImageObject, ListItem, Organization, 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.