iezvu.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of iezvu.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 27838ms. 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 164 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 50/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options. However, the site is missing Strict-Transport-Security (HSTS), 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 7 technologies across 5 categories powering iezvu.com. The detected stack includes React, Vue.js, Google Analytics 4, Hotjar 5029241, Cloudflare Turnstile, Cloudflare, and Adobe Fonts. The UI is built with React.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, iezvu.com receives an overall trust score of 64/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time27838ms
ProtocolHTTP/2
Page Size164 KB
CompressionNone
Compression SavingsN/A
CDNNo
Servernginx/1.16.0
Total Requests201
3rd Party Domains25
Redirect1 hop(s)
Detected Technologies (7)
⚛️ React
⚛️ Vue.js
📊 Google Analytics 4
📊 Hotjar
🔒 Cloudflare Turnstile
☁️ Cloudflare
🔤 Adobe Fonts
Security Headers
✓
Content-Security-Policy
Set ✓
✗
Strict-Transport-Security (HSTS)
Not set
✓
X-Content-Type-Options
Set ✓
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerSectigo Limited
Issuer FullcountryName=GB, organizationName=Sectigo Limited, commonName=Sectigo Public Server Authentication CA DV R36
SubjectcommonName=*.iezvu.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
iezvu.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, iezvu.com receives a trust score of 64/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, and DMARC email authentication with a quarantine policy.
Areas of concern include: 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 iezvu.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=quarantine)
⚠️ DNSSEC not enabled
⚠️ 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
iezvu.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned iezvu.com and identified 7 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.
UI Library: React and Vue.js — handles the user interface rendering and component management for iezvu.com.
Analytics: Google Analytics 4 and Hotjar (version 5029241) — tracks visitor behavior and provides traffic insights for iezvu.com.
Security: Cloudflare Turnstile — provides security features like bot detection and CAPTCHA for iezvu.com.
CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for iezvu.com.
Fonts: Adobe Fonts — delivers web fonts for typography for iezvu.com.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-J95RDTC13S and Hotjar Site ID 5029241. These IDs can be used to identify other websites operated by the same organization.
UI Library
⚛️ React(95%)⚛️ Vue.js(95%)
Analytics
📊 Google Analytics 4(95%)📊 Hotjar 5029241(100%)
Security
🔒 Cloudflare Turnstile(95%)
CDN
Fonts
Tracking IDs
ga4_idG-J95RDTC13S
hotjar_id5029241
iezvu.com Performance, Speed & Core Web Vitals
🤖 AI Summary
iezvu.com delivers its homepage in 27838ms (server response time), which is considered slow by industry standards. The total page weight is 164 KB, and we detected 201 resource requests loading assets from 25 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 iezvu.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: 0 out of 5 CSS files and 1 out of 8 JavaScript files are minified. Minifying the remaining 12 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 iezvu.com produces approximately 0.08g 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 164 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for iezvu.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.08g
RatingA
Page Weight & Optimization
HTML Size164 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests201
3rd Party Domains25
CSS Minified0/5
JS Minified1/8
iezvu.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
iezvu.com resolves to the IPv4 address 52.83.158.213, 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: ns-1472.awsdns-56.org, ns-1554.awsdns-02.co.uk, ns-221.awsdns-27.com, and ns-823.awsdns-38.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.
Email for iezvu.com is handled by qq.com with 2 MX records configured: mxbiz1.qq.com and mxbiz2.qq.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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 iezvu.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 iezvu.com: blog.iezvu.com, cdn.iezvu.com, and www.iezvu.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns-1472.awsdns-56.org
ns-1554.awsdns-02.co.uk
ns-221.awsdns-27.com
ns-823.awsdns-38.net
MX
mxbiz1.qq.com
mxbiz2.qq.com
Email & Authentication
MX Providerqq.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (3 found)
blog.iezvu.com cdn.iezvu.com www.iezvu.com
iezvu.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of iezvu.com contains 418 words of visible text content. This is a moderate amount of content. The page is structured with 2 H2 headings, 6 H3 headings, 12 H4 headings, 5 H5, and 0 H6 headings.
The page includes 60 images. 32 images (53%) 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 47% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 61 internal links pointing to other pages on the same domain and 26 external links pointing to third-party websites. There are 8 external JavaScript files, 5 CSS stylesheets, and 0 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.
The website has social media presence across 4 platforms: Facebook (@iezcast), Instagram (@ezcast_), Linkedin (@ezcast), and Youtube (@UCrzaLjA1EiiBiYR4VKCoZpA). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1CamCast
H2 Tags2
H3 Tags6
H4 Tags12
H5 Tags5
H6 Tags0
Internal Links61
External Links26
Assets & Features
JavaScript Files8
JS Minified1/8
CSS Files5
CSS Minified0/5
Iframes0
Images60
Missing Alt32
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @iezcastInstagram: @ezcast_Linkedin: @ezcastYoutube: @UCrzaLjA1EiiBiYR4VKCoZpA
iezvu.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for iezvu.com is good at 69 characters: "EZCast | Wireless Display Solutions for Lifestyle, Meetings & Cameras". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 144 characters (well-optimized): "EZCast is a wireless device that plugs into any screen, HDTV or projector to display wireless media to the screen from s...". 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 index, follow and a favicon is configured.
Open Graph meta tags are configured with 1/4 recommended fields: OG image (social sharing thumbnail), These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.
The meta keywords tag contains 1 terms including EZCast Dongle | WiFi Display Dongle | MiraCast | DLNA | AirPlay | wireless | hdmi streaming | video | miracast | dongle | wireless display | live video streaming | wireless dongle | wireless display transmitter | streaming media player | dlna player Tv Dongle | Miracast Dongle Adapter | Miracast Streaming Device | Miracast Devices. 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
EZCast | Wireless Display Solutions for Lifestyle, Meetings & Cameras
https://iezvu.com
EZCast is a wireless device that plugs into any screen, HDTV or projector to display wireless media to the screen from smartphones and laptops.
Meta Tags
TitleEZCast | Wireless Display Solutions for Lifestyle, Meetings ...
Title Length69 chars
Meta Desc Length144 chars
H1CamCast
Language—
Canonical—
Meta Robotsindex, follow
Meta KeywordsEZCast Dongle | WiFi Display Dongle | MiraCast | DLNA | AirP...
Schema.org & Social
Schema Types—
OG Type—
OG ImageSet ✓
Twitter Card—
FaviconSet ✓
Open Graph Preview
iezvu.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 iezvu.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-J95RDTC13S, hotjar_id: 5029241.
Tracking IDs for Cross-Referencing
ga4_idG-J95RDTC13S
hotjar_id5029241
Related Domains
Related domain data requires database (populated after batch crawl)