autofine.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of autofine.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 67862ms. 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 150 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-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 5 technologies across 5 categories powering autofine.com. The detected stack includes WordPress 7.0, StackPath, Google Fonts, jQuery 1.11.0., and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, autofine.com receives an overall trust score of 61/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time67862ms
ProtocolHTTP/2
Page Size150 KB
CompressionNone
Compression SavingsN/A
CDNNo
Servernginx
Total Requests190
3rd Party Domains6
Redirect1 hop(s)
Detected Technologies (5)
• WordPress
☁️ StackPath
🔤 Google Fonts
📦 jQuery
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✓
X-Content-Type-Options
Set ✓
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=YR1
SubjectcommonName=autofine.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
autofine.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, autofine.com receives a trust score of 61/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification.
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 autofine.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.
Trust Signals
✅ Valid HTTPS
✅ SPF configured
✅ DMARC configured (p=none)
✅ DKIM configured
⚠️ 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
autofine.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned autofine.com and identified 5 distinct technologies across 5 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 7.0) — manages the content and page structure for autofine.com.
CDN: StackPath — accelerates content delivery by caching assets at edge locations worldwide for autofine.com.
Fonts: Google Fonts — delivers web fonts for typography for autofine.com.
JavaScript Library: jQuery (version 1.11.0.) — provides utility functions and DOM manipulation for autofine.com.
Icon Set: Font Awesome — provides additional functionality for autofine.com.
CMS
CDN
Fonts
JavaScript Library
Icon Set
autofine.com Performance, Speed & Core Web Vitals
🤖 AI Summary
autofine.com delivers its homepage in 67862ms (server response time), which is considered slow by industry standards. The total page weight is 150 KB, and we detected 190 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 autofine.com. 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: 3 out of 11 CSS files and 14 out of 19 JavaScript files are minified. Minifying the remaining 13 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 autofine.com produces approximately 0.07g 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 150 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for autofine.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.07g
RatingA
Page Weight & Optimization
HTML Size150 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests190
3rd Party Domains6
CSS Minified3/11
JS Minified14/19
autofine.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
autofine.com resolves to the IPv4 address 160.16.96.54, 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: ns1.dnsb-do.jp and ns2.i-do.ne.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 autofine.com is handled by autofine.com with 1 MX records configured: mail.autofine.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 (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 autofine.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.
Our subdomain enumeration scan discovered 3 active subdomains for autofine.com: mail.autofine.com, webmail.autofine.com, and www.autofine.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns1.dnsb-do.jp
ns2.i-do.ne.jp
Email & Authentication
MX Providerautofine.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (3 found)
mail.autofine.com webmail.autofine.com www.autofine.com
autofine.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of autofine.com contains 594 words of visible text content. This is a moderate amount of content. The page is structured with 31 H2 headings, 8 H3 headings, 15 H4 headings, 4 H5, and 0 H6 headings.
The page includes 57 images. 31 images (54%) 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 46% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 70 internal links pointing to other pages on the same domain and 23 external links pointing to third-party websites. There are 19 external JavaScript files, 11 CSS stylesheets, and 0 iframes on the page.
The site implements the following web standards and features: RSS feed for content syndication.
Notable missing features: XML Sitemap, 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 2 platforms: Facebook (@M3ALPINA) and Instagram (@autofine). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1autofine
H2 Tags31
H3 Tags8
H4 Tags15
H5 Tags4
H6 Tags0
Internal Links70
External Links23
Assets & Features
JavaScript Files19
JS Minified14/19
CSS Files11
CSS Minified3/11
Iframes0
Images57
Missing Alt31
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedYes ✓
Social Media Presence
Facebook: @M3ALPINAInstagram: @autofine
autofine.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for autofine.com is well-optimized at 56 characters: "BMW 修理やALPINA(アルピナ) 修理・車検・整備・新車中古車販売専門店のオートファイン 神奈川県【横浜】". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
No meta description is configured for autofine.com. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended.
The canonical url is correctly set to https://www.autofine.com, preventing duplicate content issues and the meta robots directive is set to max-snippet:-1, max-image-preview:large, max-video-preview:-1.
Open Graph meta tags are configured with 2/4 recommended fields: OG title ("BMW 修理やALPINA(アルピナ) 修理・車検・整備・新車中古車販売専門店のオートファイン 神奈川県【横浜】..."), 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 meta keywords tag contains 12 terms including bmw 修理, alpina 修理, bmw 専門店, bmw m3, 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
BMW 修理やALPINA(アルピナ) 修理・車検・整備・新車中古車販売専門店のオートファイン 神奈川県【横浜】
https://autofine.com
Meta Tags
TitleBMW 修理やALPINA(アルピナ) 修理・車検・整備・新車中古車販売専門店のオートファイン 神奈川県【横浜】...
Title Length56 chars
Meta Desc Length0 chars
H1autofine
Language—
Canonicalhttps://www.autofine.com
Meta Robotsmax-snippet:-1, max-image-preview:large, max-video-preview:-1
Meta Keywordsbmw 修理,alpina 修理,bmw 専門店,bmw m3,修理工場,中古車,車検,整備,メンテナンス,神奈川県,横...
Schema.org & Social
Schema Types—
OG Typearticle
OG ImageNot set
Twitter Cardsummary
FaviconNot set