my819.jp Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of my819.jp on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 15360ms. 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 7 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 my819.jp. The detected stack includes Google Tag Manager, Google Fonts, and jQuery.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, my819.jp receives an overall trust score of 53/100, classified as "Caution Advised".
HTTP Response
Status200 OK
Response Time15360ms
ProtocolHTTP/1.1
Page Size7 KB
CompressionNone
Compression SavingsN/A
CDNNo
ServerApache
Total Requests22
3rd Party Domains4
Redirect1 hop(s)
Detected Technologies (3)
🏷️ Google Tag Manager
🔤 Google Fonts
📦 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
IssuerNijimo, Inc.
Issuer FullcountryName=JP, organizationName=Nijimo, Inc., commonName=FujiSSL RSA Domain Validation Secure Server CA 2
SubjectcommonName=my819.jp
Type—
TLS VersionTLS 1.2
Cipher SuiteECDHE-RSA-AES256-GCM-SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
my819.jp Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, my819.jp receives a trust score of 53/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.
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 my819.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
⚠️ 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
my819.jp Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned my819.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.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for my819.jp.
Fonts: Google Fonts — delivers web fonts for typography for my819.jp.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for my819.jp.
We also extracted the following tracking identifiers: Google Tag Manager container GTM-WPQS69. These IDs can be used to identify other websites operated by the same organization.
Tag Manager
🏷️ Google Tag Manager(95%)
Fonts
JavaScript Library
Tracking IDs
my819.jp Performance, Speed & Core Web Vitals
🤖 AI Summary
my819.jp delivers its homepage in 15360ms (server response time), which is considered slow by industry standards. The total page weight is 7 KB, and we detected 22 resource requests loading assets from 4 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 my819.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 2 CSS files and 1 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 my819.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 7 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for my819.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 Size7 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests22
3rd Party Domains4
CSS Minified0/2
JS Minified1/2
my819.jp DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
my819.jp resolves to the IPv4 address 163.43.251.158, 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 4 name servers: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, and 04.dnsv.jp. 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 my819.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.
DNS Records
NS
01.dnsv.jp
02.dnsv.jp
03.dnsv.jp
04.dnsv.jp
Email & Authentication
MX Provider—
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
my819.jp Page Content, Images & Accessibility
🤖 AI Summary
The homepage of my819.jp contains 23 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, 1 H3 headings, 2 H4 headings.
The page includes 10 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 4 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 2 external JavaScript files, 2 CSS stylesheets, and 1 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お客様専用ページ「マイ819(バイク)」へようこそ
H2 Tags1
H3 Tags1
H4 Tags2
H5 Tags0
H6 Tags0
Internal Links4
External Links1
Assets & Features
JavaScript Files2
JS Minified1/2
CSS Files2
CSS Minified0/2
Iframes1
Images10
Missing Alt0
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
my819.jp SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for my819.jp is well-optimized at 31 characters: "マイ819(マイバイク)|ZuttoRideClub会員サイト". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
The meta description is 108 characters (well-optimized): "はじめてマイ819(マイバイク)をご利用される方は利用登録をすることができます。既にマイ819(マイバイク)に登録されている方のログインもこちらから。レジャー・宿泊施設割引、プレゼント抽選、陸送割引など特典満載です!". 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.
A favicon is configured.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("マイ819..."), 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.
Google SERP Preview
マイ819(マイバイク)|ZuttoRideClub会員サイト
https://my819.jp
はじめてマイ819(マイバイク)をご利用される方は利用登録をすることができます。既にマイ819(マイバイク)に登録されている方のログインもこちらから。レジャー・宿泊施設割引、プレゼント抽選、陸送割引など特典満載です!
Meta Tags
Titleマイ819(マイバイク)|ZuttoRideClub会員サイト...
Title Length31 chars
Meta Desc Length108 chars
H1お客様専用ページ「マイ819(バイク)」へようこそ
Language—
Canonical—
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageSet ✓
Twitter Card—
FaviconSet ✓
Open Graph Preview
my819.jp
マイ819
はじめてマイ819(マイバイク)をご利用される方は利用登録をすることができます。既にマイ819(マイバイク)に登録されている方のログインもこちらから。レジャー・宿泊施設割引、プレゼント抽選、陸送割引など特典満載です!
my819.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 my819.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: gtm_id: GTM-WPQS69.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)