ainobinbo.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of ainobinbo.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 23923ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 12 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 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 5 technologies across 5 categories powering ainobinbo.com. The detected stack includes Bootstrap 5.3.0, Google Analytics 4, Google AdSense, Google Fonts, and jQuery 3.7.1..
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ainobinbo.com receives an overall trust score of 60/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time23923ms
ProtocolHTTP/2
Page Size12 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
ServerApache
Total Requests44
3rd Party Domains11
RedirectNone
Detected Technologies (5)
🎨 Bootstrap
📊 Google Analytics 4
📢 Google AdSense
🔤 Google Fonts
📦 jQuery
Security Headers
✗
Content-Security-Policy
Not set
✓
Strict-Transport-Security (HSTS)
Set ✓
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=R12
SubjectcommonName=ainobinbo.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
ainobinbo.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, ainobinbo.com receives a trust score of 60/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, and SPF (Sender Policy Framework) email authentication preventing email spoofing.
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 ainobinbo.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
✅ HSTS enabled
✅ SPF configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
⚠️ 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
ainobinbo.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned ainobinbo.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.
CSS Framework: Bootstrap (version 5.3.0) — provides the styling and responsive layout system for ainobinbo.com.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for ainobinbo.com.
Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for ainobinbo.com.
Fonts: Google Fonts — delivers web fonts for typography for ainobinbo.com.
JavaScript Library: jQuery (version 3.7.1.) — provides utility functions and DOM manipulation for ainobinbo.com.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-WS7BDZ6V4X. These IDs can be used to identify other websites operated by the same organization.
CSS Framework
Analytics
📊 Google Analytics 4(95%)
Advertising
Fonts
JavaScript Library
Tracking IDs
ainobinbo.com Performance, Speed & Core Web Vitals
🤖 AI Summary
ainobinbo.com delivers its homepage in 23923ms (server response time), which is considered slow by industry standards. The total page weight is 12 KB, and we detected 44 resource requests loading assets from 11 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: 1 out of 8 CSS files and 3 out of 12 JavaScript files are minified. Minifying the remaining 16 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 ainobinbo.com produces approximately 0.01g 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 12 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ainobinbo.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.01g
RatingA
Page Weight & Optimization
HTML Size12 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests44
3rd Party Domains11
CSS Minified1/8
JS Minified3/12
ainobinbo.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
ainobinbo.com resolves to the IPv4 address 202.172.28.31, 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.value-domain.com and ns2.value-domain.com. 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 ainobinbo.com is handled by ainobinbo.com with 1 MX records configured: ainobinbo.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 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 ainobinbo.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 25 active subdomains for ainobinbo.com: admin.ainobinbo.com, api.ainobinbo.com, app.ainobinbo.com, apps.ainobinbo.com, blog.ainobinbo.com, cdn.ainobinbo.com, community.ainobinbo.com, and dev.ainobinbo.com. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns1.value-domain.com
ns2.value-domain.com
Email & Authentication
MX Providerainobinbo.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (25 found)
admin.ainobinbo.com api.ainobinbo.com app.ainobinbo.com apps.ainobinbo.com blog.ainobinbo.com cdn.ainobinbo.com community.ainobinbo.com dev.ainobinbo.com developers.ainobinbo.com docs.ainobinbo.com ftp.ainobinbo.com help.ainobinbo.com m.ainobinbo.com mail.ainobinbo.com partners.ainobinbo.com portal.ainobinbo.com shop.ainobinbo.com smtp.ainobinbo.com staging.ainobinbo.com static.ainobinbo.com status.ainobinbo.com store.ainobinbo.com support.ainobinbo.com webmail.ainobinbo.com www.ainobinbo.com
ainobinbo.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of ainobinbo.com contains 52 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, 3 H3 headings, 0 H4 headings.
The page includes 4 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content).
The link structure consists of 13 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 12 external JavaScript files, 8 CSS stylesheets, and 0 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: Instagram (@takosaki_takoyaki). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1—
H2 Tags0
H3 Tags3
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links13
External Links6
Assets & Features
JavaScript Files12
JS Minified3/12
CSS Files8
CSS Minified1/8
Iframes0
Images4
Missing Alt0
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Instagram: @takosaki_takoyaki
ainobinbo.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for ainobinbo.com is good at 18 characters: "愛の貧乏脱出大作戦 非公式応援ページ". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 19 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://ainobinbo.com/, preventing duplicate content issues, the page language is declared as ja, and the meta robots directive is set to index,follow.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("愛の貧乏脱出大作戦 非公式応援ページ..."), 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.
Google SERP Preview
愛の貧乏脱出大作戦 非公式応援ページ
https://ainobinbo.com
愛の貧乏脱出大作戦 非公式応援ページ
Meta Tags
Title愛の貧乏脱出大作戦 非公式応援ページ...
Title Length18 chars
Meta Desc Length19 chars
H1—
Languageja
Canonicalhttps://ainobinbo.com/
Meta Robotsindex,follow
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageSet ✓
Twitter Cardsummary
FaviconNot set
Open Graph Preview
ainobinbo.com
愛の貧乏脱出大作戦 非公式応援ページ
このホームページは、1998年から2002年まで、テレビ東京系列で放映された「愛の貧乏脱出大作戦」に出場した貧乏店を可能な限り実地調査し、「その後のその後」情報を交換するページです。
ainobinbo.com 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 ainobinbo.com. 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-WS7BDZ6V4X.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)