autograph.co.jp Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of autograph.co.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 1928ms. The page is served over HTTP/1.1 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 8 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 3 technologies across 3 categories powering autograph.co.jp. The detected stack includes Google Analytics 4, Cloudflare, and jQuery.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, autograph.co.jp receives an overall trust score of 59/100, classified as "Caution Advised".
HTTP Response
Status200 OK
Response Time1928ms
ProtocolHTTP/1.1
Page Size8 KB
CompressionNone
Compression SavingsN/A
CDNNo
ServerApache
Total Requests11
3rd Party Domains2
RedirectNone
Detected Technologies (3)
📊 Google Analytics 4
☁️ Cloudflare
📦 jQuery
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGlobalSign nv-sa
Issuer FullcountryName=BE, organizationName=GlobalSign nv-sa, commonName=GlobalSign GCC R3 DV TLS CA 2020
SubjectcommonName=www.autograph.co.jp
Type—
TLS VersionTLS 1.2
Cipher SuiteECDHE-RSA-AES256-GCM-SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
autograph.co.jp Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, autograph.co.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, 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 autograph.co.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.
Trust Signals
✅ Valid HTTPS
✅ SPF configured
✅ DMARC configured (p=none)
⚠️ DNSSEC not enabled
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
autograph.co.jp Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned autograph.co.jp and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for autograph.co.jp.
CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for autograph.co.jp.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for autograph.co.jp.
Analytics
📊 Google Analytics 4(95%)
CDN
JavaScript Library
autograph.co.jp Performance, Speed & Core Web Vitals
🤖 AI Summary
autograph.co.jp delivers its homepage in 1928ms (server response time), which is considered somewhat slow by industry standards. The total page weight is 8 KB, and we detected 11 resource requests loading assets from 2 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 autograph.co.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 2 out of 2 JavaScript files are minified. Minifying the remaining 3 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 autograph.co.jp produces approximately 0.0g 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 8 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for autograph.co.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.0g
RatingA
Page Weight & Optimization
HTML Size8 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests11
3rd Party Domains2
CSS Minified0/3
JS Minified2/2
autograph.co.jp DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
autograph.co.jp resolves to the IPv4 address 111.89.140.42, 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: ns3.sphere.ad.jp and ns4.sphere.ad.jp. 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 autograph.co.jp is handled by co.jp with 1 MX records configured: autograph.co.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 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 autograph.co.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 2 active subdomains for autograph.co.jp: ftp.autograph.co.jp and www.autograph.co.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns3.sphere.ad.jp
ns4.sphere.ad.jp
Email & Authentication
MX Providerco.jp
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (2 found)
ftp.autograph.co.jp www.autograph.co.jp
autograph.co.jp Page Content, Images & Accessibility
🤖 AI Summary
The homepage of autograph.co.jp contains 82 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 1 H2 headings, 0 H3 headings, 0 H4 headings.
The page includes 4 images. 1 images (25%) 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 75% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 2 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 2 external JavaScript files, 3 CSS stylesheets, and 0 iframes on the page.
Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
Content Structure
H1—
H2 Tags1
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links2
External Links0
Assets & Features
JavaScript Files2
JS Minified2/2
CSS Files3
CSS Minified0/3
Iframes0
Images4
Missing Alt1
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
autograph.co.jp SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for autograph.co.jp is good at 18 characters: "スタジオ オートグラフ:恵比寿・神泉". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 30 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 page language is declared as ja and the meta robots directive is set to index,follow,noarchive.
No Open Graph tags are configured. When someone shares a link to autograph.co.jp 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 8 terms including スタジオ オートグラフ, STUDIO AUTOGRAPH, 撮影スタジオ, ホリゾント, 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.
Google SERP Preview
スタジオ オートグラフ:恵比寿・神泉
https://autograph.co.jp
撮影用ホリゾントスタジオ、スタジオオートグラフ 恵比寿・神泉
Meta Tags
Titleスタジオ オートグラフ:恵比寿・神泉...
Title Length18 chars
Meta Desc Length30 chars
H1—
Languageja
Canonical—
Meta Robotsindex,follow,noarchive
Meta Keywordsスタジオ オートグラフ,STUDIO AUTOGRAPH,撮影スタジオ,ホリゾント,ホリゾントスタジオ,STUDIO,フ...
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconNot set