evozi.com

HTTPS HTTP/2 Gzip Cloudflare Next.js Crawled in 52,998ms · June 27, 2026 18:45 UTC

evozi.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of evozi.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 24626ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 67 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 4 technologies across 4 categories powering evozi.com. The detected stack includes Next.js css, React, Webpack, and Cloudflare. The site uses Next.js as its primary framework (version css). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, evozi.com receives an overall trust score of 58/100, classified as "Caution Advised".
58
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time24626ms
ProtocolHTTP/2
Page Size67 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests44
3rd Party Domains4
Redirect2 hop(s)
Detected Technologies (4)
🔧 Next.js ⚛️ React 🔨 Webpack ☁️ Cloudflare
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=evozi.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

evozi.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, evozi.com receives a trust score of 58/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, DMARC email authentication with a quarantine 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 evozi.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.
58
/ 100
Caution Advised
Trust Signals
Valid HTTPS
DMARC configured (p=quarantine)
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

evozi.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned evozi.com and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version css) — provides the application framework and routing for evozi.com. UI Library: React — handles the user interface rendering and component management for evozi.com. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for evozi.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for evozi.com.
Framework
🔧 Next.js css(100%)
UI Library
⚛️ React(95%)
Build Tool
🔨 Webpack(95%)
CDN
☁️ Cloudflare(100%)

evozi.com Performance, Speed & Core Web Vitals

🤖 AI Summary
evozi.com delivers its homepage in 24626ms (server response time), which is considered slow by industry standards. The total page weight is 67 KB, and we detected 44 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. 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: 0 out of 1 CSS files and 1 out of 10 JavaScript files are minified. Minifying the remaining 10 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 evozi.com produces approximately 0.03g 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 67 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for evozi.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.03g
RatingA
Page Weight & Optimization
HTML Size67 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests44
3rd Party Domains4
CSS Minified0/1
JS Minified1/10

evozi.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
evozi.com resolves to the IPv4 address 172.67.191.217 and also supports IPv6 (2606:4700:3031::6815:1443), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: norm.ns.cloudflare.com and vera.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 evozi.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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 evozi.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 5 active subdomains for evozi.com: api.evozi.com, apps.evozi.com, mail.evozi.com, support.evozi.com, and www.evozi.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
172.67.191.217
104.21.20.67
AAAA
2606:4700:3031::6815:1443
NS
norm.ns.cloudflare.com
vera.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=quarantine
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (5 found)
api.evozi.com apps.evozi.com mail.evozi.com support.evozi.com www.evozi.com

evozi.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of evozi.com contains 289 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 3 H2 headings, 1 H3 headings, 4 H4 headings, 5 H5, and 6 H6 headings. The page includes 3 images. 2 images (67%) 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 33% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 10 internal links pointing to other pages on the same domain and 9 external links pointing to third-party websites. There are 10 external JavaScript files, 1 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 3 platforms: Facebook (@evozi), Twitter (@evozi), and Github (@evozi). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
289
Words
3
Images
33%
Alt Text Score
67
Page Size (KB)
Content Structure
H1Create What's Next
H2 Tags3
H3 Tags1
H4 Tags4
H5 Tags5
H6 Tags6
Internal Links10
External Links9
Assets & Features
JavaScript Files10
JS Minified1/10
CSS Files1
CSS Minified0/1
Iframes0
Images3
Missing Alt2
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @evoziTwitter: @evoziGithub: @evozi

evozi.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for evozi.com is good at 26 characters: "Evozi | Create What's Next". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 45 characters (acceptable): "We love to create simple & intuitive products". 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 page language is declared as en. No Open Graph tags are configured. When someone shares a link to evozi.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.
Google SERP Preview
Evozi | Create What's Next
https://evozi.com
We love to create simple & intuitive products
Meta Tags
TitleEvozi | Create What's Next...
Title Length26 chars
Meta Desc Length45 chars
H1Create What's Next
Languageen
Canonical
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconNot set