naotabi.com

We performed a comprehensive analysis of naotabi.com on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 70339ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 275 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-09-23, which is 86 days from now. The security headers analysis reveals a score of 15/100 (poor). The following security headers are properly configured: X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-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 6 technologies across 6 categories powering naotabi.com. The detected stack includes WordPress, Next.js, Google Analytics 4, Google AdSense, reCAPTCHA v3, and Google Fonts. The site uses Next.js as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, naotabi.com receives an overall trust score of 65/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, naotabi.com receives a trust score of 65/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 Let's Encrypt with 86 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, and a domain registered for 4.7 years. 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 naotabi.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. The domain is registered through GMO Internet Group, Inc. d/b/a Onamae.com based in JP, with a registration date of 2021-10-04 and expiration date of 2026-10-04.

Our technology detection engine scanned naotabi.com and identified 6 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 — manages the content and page structure for naotabi.com. Framework: Next.js — provides the application framework and routing for naotabi.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for naotabi.com. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for naotabi.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for naotabi.com. Fonts: Google Fonts — delivers web fonts for typography for naotabi.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-Z6CCDL31H3. These IDs can be used to identify other websites operated by the same organization.

naotabi.com delivers its homepage in 70339ms (server response time), which is considered slow by industry standards. The total page weight is 275 KB, and we detected 128 resource requests loading assets from 4 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 12 out of 18 JavaScript files are minified. Minifying the remaining 14 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 naotabi.com produces approximately 0.13g 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 275 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for naotabi.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.

naotabi.com resolves to the IPv4 address 118.27.122.254, 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 3 name servers: ns-a1.conoha.io, ns-a2.conoha.io, and ns-a3.conoha.io. Having 3 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 naotabi.com is handled by ne.jp with 1 MX records configured: mail77.conoha.ne.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 (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 naotabi.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 domain is registered through GMO Internet Group, Inc. d/b/a Onamae.com (JP). It was first registered on 2021-10-04 and is set to expire on 2026-10-04, making it 4.7 years old. Our subdomain enumeration scan discovered 2 active subdomains for naotabi.com: mail.naotabi.com and www.naotabi.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of naotabi.com contains 179 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 25 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 29 images. 2 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 63 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 18 external JavaScript files, 8 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (ImageObject, Organization, SearchAction, and WebSite) and RSS feed for content syndication. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for naotabi.com is well-optimized at 32 characters: "ナオコは明日、旅に出る | 旅の計画に役立つ情報をお届けします。". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 52 characters (acceptable): "国内旅行、海外旅行、その他旅する際に役立つ情報のサイトです。明日旅に出たくなるような情報をお届けします。". 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://naotabi.com/, preventing duplicate content issues, the page language is declared as ja, the meta robots directive is set to max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("ナオコは明日、旅に出る | 旅の計画に役立つ情報をお届けします。..."), 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_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" 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: ImageObject, Organization, SearchAction, 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.