addict-tokyo.jp

We performed a comprehensive analysis of addict-tokyo.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 44043ms. The page is served over HTTP/2 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 35 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 15/100 (poor). The following security headers are properly configured: X-Frame-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 4 technologies across 4 categories powering addict-tokyo.jp. The detected stack includes WordPress, Google Analytics 4, Google Tag Manager, and Adobe Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, addict-tokyo.jp receives an overall trust score of 59/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, addict-tokyo.jp receives a trust score of 59/100, which places it in the "Caution Advised" 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, and DMARC email authentication with a none policy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 addict-tokyo.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 addict-tokyo.jp and identified 4 distinct technologies across 4 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 addict-tokyo.jp. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for addict-tokyo.jp. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for addict-tokyo.jp. Fonts: Adobe Fonts — delivers web fonts for typography for addict-tokyo.jp. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-7VWB8JRVBN and Google Tag Manager container GTM-NQ7DT8S. These IDs can be used to identify other websites operated by the same organization.

addict-tokyo.jp delivers its homepage in 44043ms (server response time), which is considered slow by industry standards. The total page weight is 35 KB, and we detected 103 resource requests loading assets from 6 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. No compression is currently enabled on addict-tokyo.jp. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 3 CSS files and 0 out of 3 JavaScript files are minified. Minifying the remaining 6 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 addict-tokyo.jp produces approximately 0.02g 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 35 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for addict-tokyo.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.

addict-tokyo.jp resolves to the IPv4 address 16.76.22.57, 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 2 A record(s) configured. The domain name system is managed by 4 name servers: ns-1404.awsdns-47.org, ns-2005.awsdns-58.co.uk, ns-281.awsdns-35.com, and ns-873.awsdns-45.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 addict-tokyo.jp is handled by pphosted.com with 2 MX records configured: mxa-007f0c01.gslb.pphosted.com and mxb-007f0c01.gslb.pphosted.com. 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 addict-tokyo.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 addict-tokyo.jp contains 279 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 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 56 images. 25 images (45%) 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 55% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 23 internal links pointing to other pages on the same domain and 11 external links pointing to third-party websites. There are 3 external JavaScript files, 3 CSS stylesheets, and 3 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages). Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 1 platforms: Facebook (@addict.tokyo.jp). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for addict-tokyo.jp is well-optimized at 39 characters: "addict | Experience & Innovation Design". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 118 characters (well-optimized): "addictは、Experience DesignとInnovation Designに強みを持つクリエイティブブティックです。 Creative×Technology×Business を起点に生活者の“新しい体験価値”を創造します。". 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 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 4/4 recommended fields: OG title ("addict | Experience & Innovation Design..."), 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. 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 meta keywords tag contains 11 terms including addict, イノベーションデザイン, 藤本勝也, 植田誠, 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.