HomeDirectory Oozyoyo.com

ozyoyo.com

HTTPS HTTP/2 Gzip Cloudflare Crawled in 88,434ms · June 28, 2026 01:42 UTC

ozyoyo.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of ozyoyo.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 26272ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 5.3% size reduction. The total page weight is 141 KB, and the site is served behind a CDN (Content Delivery Network). 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 ozyoyo.com. The detected stack includes Google Analytics 4, Cloudflare, and jQuery 1.11.0.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ozyoyo.com receives an overall trust score of 53/100, classified as "Caution Advised".
53
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time26272ms
ProtocolHTTP/2
Page Size141 KB
CompressionGzip
Compression Savings~5.3%
CDNYes ✓
Servercloudflare
Total Requests605
3rd Party Domains6
Redirect3 hop(s)
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
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=ozyoyo.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

ozyoyo.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, ozyoyo.com 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 ozyoyo.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.
53
/ 100
Caution Advised
Trust Signals
Valid HTTPS
⚠️ DNSSEC not enabled
Sitemap.xml found
Robots.txt 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

ozyoyo.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned ozyoyo.com 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 ozyoyo.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for ozyoyo.com. JavaScript Library: jQuery (version 1.11.0.) — provides utility functions and DOM manipulation for ozyoyo.com.
Analytics
📊 Google Analytics 4(95%)
CDN
☁️ Cloudflare(100%)
JavaScript Library
📦 jQuery 1.11.0.(100%)

ozyoyo.com Performance, Speed & Core Web Vitals

🤖 AI Summary
ozyoyo.com delivers its homepage in 26272ms (server response time), which is considered slow by industry standards. The total page weight is 141 KB, and we detected 605 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. The website uses Gzip compression for text-based assets, achieving an estimated 5.3% 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 10 CSS files and 3 out of 15 JavaScript files are minified. Minifying the remaining 21 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. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of ozyoyo.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 141 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ozyoyo.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 Size141 KB
CompressionGzip
Compression Savings~5.3%
CDNYes ✓
Total Requests605
3rd Party Domains6
CSS Minified1/10
JS Minified3/15

ozyoyo.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
ozyoyo.com resolves to the IPv4 address 104.21.70.54 and also supports IPv6 (2606:4700:3035::ac43:dc6e), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: ray.ns.cloudflare.com and sara.ns.cloudflare.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 ozyoyo.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. 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 ozyoyo.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 1 active subdomains for ozyoyo.com: www.ozyoyo.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
104.21.70.54
172.67.220.110
AAAA
2606:4700:3035::ac43:dc6e
NS
ray.ns.cloudflare.com
sara.ns.cloudflare.com
MX
aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
aspmx2.googlemail.com
aspmx3.googlemail.com
Email & Authentication
SPF
DMARC p=—
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (1 found)
www.ozyoyo.com

ozyoyo.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of ozyoyo.com contains 1,380 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 1 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 115 images. 115 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 462 internal links pointing to other pages on the same domain and 2 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 15 external JavaScript files, 10 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) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
1,380
Words
115
Images
0%
Alt Text Score
141
Page Size (KB)
Content Structure
H1
H2 Tags1
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links462
External Links2
Assets & Features
JavaScript Files15
JS Minified3/15
CSS Files10
CSS Minified1/10
Iframes0
Images115
Missing Alt115
SitemapYes ✓
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo

ozyoyo.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for ozyoyo.com is too long at 113 characters: "OZYOYO中文网|布里斯班bbs论坛_BrisbaneBBS_OZYOYO中文网_黄金海岸论坛_Goldcoast_昆士兰_租房_工作_交友_同城 - 布里斯...". At 113 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 5 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 meta robots directive is set to noimageindex. No Open Graph tags are configured. When someone shares a link to ozyoyo.com 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 1 terms including 门户首页. 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
OZYOYO中文网|布里斯班bbs论坛_BrisbaneBBS_OZYOYO中文网_黄金海岸论坛_Goldcoast_昆士兰_租房_工作_交友_同城 - 布里斯班中文网_华人论坛_新闻_租房_求职_二手_汽车_交友_灌水_吐槽
https://ozyoyo.com
门户首页
Meta Tags
TitleOZYOYO中文网|布里斯班bbs论坛_BrisbaneBBS_OZYOYO中文网_黄金海岸论坛_Goldcoast_昆...
Title Length113 chars
Meta Desc Length5 chars
H1
Language
Canonical
Meta Robotsnoimageindex
Meta Keywords门户首页
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconNot set

ozyoyo.com Data Breaches, History, Green Hosting & Mobile Apps

🤖 AI Summary
This section shows additional intelligence about ozyoyo.com including data breach history (via HaveIBeenPwned), web archive history (Wayback Machine), green/eco-friendly hosting status, and mobile app presence in the iOS App Store.
No Data Breaches Found
This domain has not appeared in any known data breaches.
🌿
Green Hosting
Hosted by Cloudflare — verified eco-friendly hosting provider.