autoby.jp Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of autoby.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 31525ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 839 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 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-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 12 technologies across 9 categories powering autoby.jp. The detected stack includes Google Analytics 4, Microsoft Clarity, Matomo, Google Tag Manager, Meta Pixel, reCAPTCHA v3, Amazon CloudFront, Google Fonts, Vimeo, YouTube Embed, jQuery 3.7.1., and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, autoby.jp receives an overall trust score of 67/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time31525ms
ProtocolHTTP/2
Page Size839 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Servernginx
Total Requests461
3rd Party Domains23
Redirect1 hop(s)
Detected Technologies (12)
📊 Google Analytics 4
📊 Microsoft Clarity
📊 Matomo
🏷️ Google Tag Manager
📢 Meta Pixel
🔒 reCAPTCHA v3
☁️ Amazon CloudFront
🔤 Google Fonts
🎬 Vimeo
🎬 YouTube Embed
📦 jQuery
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✓
Strict-Transport-Security (HSTS)
Set ✓
✓
X-Content-Type-Options
Set ✓
✗
Permissions-Policy
Not set
SSL Certificate
IssuerAmazon
Issuer FullcountryName=US, organizationName=Amazon, commonName=Amazon RSA 2048 M04
SubjectcommonName=sans2.platisher.jp
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_128_GCM_SHA256
Algorithm—
Issued—
Expires— (? days)
SANs—
autoby.jp Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, autoby.jp receives a trust score of 67/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 HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks.
Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 autoby.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
✅ HSTS enabled
⚠️ DNSSEC not enabled
✅ Robots.txt found
⚠️ Missing Content-Security-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
autoby.jp Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned autoby.jp and identified 12 distinct technologies across 9 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, Microsoft Clarity, and Matomo — tracks visitor behavior and provides traffic insights for autoby.jp.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for autoby.jp.
Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for autoby.jp.
Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for autoby.jp.
CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for autoby.jp.
Fonts: Google Fonts — delivers web fonts for typography for autoby.jp.
Video: Vimeo and YouTube Embed — provides video hosting and playback for autoby.jp.
JavaScript Library: jQuery (version 3.7.1.) — provides utility functions and DOM manipulation for autoby.jp.
Icon Set: Font Awesome — provides additional functionality for autoby.jp.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-5CSQNG42TC, Google Tag Manager container GTM-PG57GDF, and Meta (Facebook) Pixel ID 445468662705566. These IDs can be used to identify other websites operated by the same organization.
Analytics
📊 Google Analytics 4(95%)📊 Microsoft Clarity(95%)📊 Matomo(95%)
Tag Manager
🏷️ Google Tag Manager(95%)
Advertising
Security
CDN
☁️ Amazon CloudFront(95%)
Fonts
Video
🎬 Vimeo(95%)🎬 YouTube Embed(95%)
JavaScript Library
Icon Set
Tracking IDs
ga4_idG-5CSQNG42TC
gtm_idGTM-PG57GDF
meta_pixel_id445468662705566
autoby.jp Performance, Speed & Core Web Vitals
🤖 AI Summary
autoby.jp delivers its homepage in 31525ms (server response time), which is considered slow by industry standards. The total page weight is 839 KB, and we detected 461 resource requests loading assets from 23 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: 2 out of 4 CSS files and 1 out of 4 JavaScript files are minified. Minifying the remaining 5 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 autoby.jp produces approximately 0.41g of CO₂, earning a carbon rating of D. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 839 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for autoby.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.41g
RatingD
Page Weight & Optimization
HTML Size839 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests461
3rd Party Domains23
CSS Minified2/4
JS Minified1/4
autoby.jp DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
autoby.jp resolves to the IPv4 address 18.182.225.134, 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 3 A record(s) configured.
The domain name system is managed by 4 name servers: ns-106.awsdns-13.com, ns-1133.awsdns-13.org, ns-1541.awsdns-00.co.uk, and ns-857.awsdns-43.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.
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 autoby.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 1 active subdomains for autoby.jp: www.autoby.jp. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
18.182.225.134
13.193.77.52
13.192.79.147
NS
ns-106.awsdns-13.com
ns-1133.awsdns-13.org
ns-1541.awsdns-00.co.uk
ns-857.awsdns-43.net
Email & Authentication
MX Provider—
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (1 found)
autoby.jp Page Content, Images & Accessibility
🤖 AI Summary
The homepage of autoby.jp contains 574 words of visible text content. This is a moderate amount of content. The page is structured with 22 H2 headings, 47 H3 headings, 0 H4 headings.
The page includes 89 images. 44 images (49%) 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 51% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 296 internal links pointing to other pages on the same domain and 41 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 4 external JavaScript files, 4 CSS stylesheets, and 2 iframes on the page.
The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and RSS feed for content syndication.
Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
The website has social media presence across 5 platforms: Facebook (@webautoby), Twitter (@webautoby), Instagram (@web_autoby), Youtube (@UCFdOHa5KxsLDCNCoispcBRA), and Tiktok (@webautoby). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1—
H2 Tags22
H3 Tags47
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links296
External Links41
Assets & Features
JavaScript Files4
JS Minified1/4
CSS Files4
CSS Minified2/4
Iframes2
Images89
Missing Alt44
SitemapNo
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedYes ✓
Social Media Presence
Facebook: @webautobyTwitter: @webautobyInstagram: @web_autobyYoutube: @UCFdOHa5KxsLDCNCoispcBRATiktok: @webautoby
autoby.jp SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for autoby.jp is good at 28 characters: "webオートバイ|バイクのニュース速報と情報を毎日更新!". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 40 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://www.autoby.jp/, 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 4/4 recommended fields: OG title ("webオートバイ|バイクのニュース速報と情報を毎日更新!..."), 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 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 meta keywords tag contains 4 terms including オートバイ, バイク, 原付2種, 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
webオートバイ|バイクのニュース速報と情報を毎日更新!
https://autoby.jp
オートバイ・バイクのニュースや二輪用品情報、コラムを、毎日お届けするサイトです。
Meta Tags
Titlewebオートバイ|バイクのニュース速報と情報を毎日更新!...
Title Length28 chars
Meta Desc Length40 chars
H1—
Languageja
Canonicalhttps://www.autoby.jp/
Meta Robotsmax-image-preview:large
Meta Keywordsオートバイ,バイク,原付2種,原付二種
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageSet ✓
Twitter Cardsummary
FaviconSet ✓
Open Graph Preview
autoby.jp
webオートバイ|バイクのニュース速報と情報を毎日更新!
オートバイ・バイクのニュースや二輪用品情報、コラムを、毎日お届けするサイトです。
autoby.jp Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with autoby.jp. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: ga4_id: G-5CSQNG42TC, gtm_id: GTM-PG57GDF, meta_pixel_id: 445468662705566.
Tracking IDs for Cross-Referencing
ga4_idG-5CSQNG42TC
gtm_idGTM-PG57GDF
meta_pixel_id445468662705566
Related Domains
Related domain data requires database (populated after batch crawl)