HomeDirectory Oomaze.com

omaze.com

HTTPS HTTP/2 Gzip Shopify Crawled in 49,507ms · June 28, 2026 01:24 UTC

omaze.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of omaze.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 11120ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 150 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 omaze.com. The detected stack includes Shopify, Google Tag Manager, New Relic, and YouTube Embed. The primary e-commerce platform is Shopify. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, omaze.com receives an overall trust score of 65/100, classified as "Likely Safe".
65
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time11120ms
ProtocolHTTP/2
Page Size150 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
ServerAmazonS3
Total Requests134
3rd Party Domains18
Redirect1 hop(s)
Detected Technologies (4)
🛒 Shopify 🏷️ Google Tag Manager 📡 New Relic 🎬 YouTube Embed
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
IssuerAmazon
Issuer FullcountryName=US, organizationName=Amazon, commonName=Amazon RSA 2048 M04
SubjectcommonName=omaze.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_128_GCM_SHA256
Algorithm
Issued
Expires— (? days)
SANs

omaze.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, omaze.com receives a trust score of 65/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, DMARC email authentication with a reject policy — the strongest available setting, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, and DNSSEC providing authenticated DNS responses. 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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked omaze.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.
65
/ 100
Likely Safe
Trust Signals
Valid HTTPS
SPF configured
DMARC configured (p=reject)
DKIM configured
DNSSEC 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

omaze.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned omaze.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. Ecommerce: Shopify — powers the online store and shopping functionality for omaze.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for omaze.com. Monitoring: New Relic — monitors application performance and errors for omaze.com. Video: YouTube Embed — provides video hosting and playback for omaze.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-K2ZCQM2. These IDs can be used to identify other websites operated by the same organization.
Ecommerce
🛒 Shopify(95%)
Tag Manager
🏷️ Google Tag Manager(95%)
Monitoring
📡 New Relic(95%)
Video
🎬 YouTube Embed(95%)
Tracking IDs
gtm_idGTM-K2ZCQM2

omaze.com Performance, Speed & Core Web Vitals

🤖 AI Summary
omaze.com delivers its homepage in 11120ms (server response time), which is considered slow by industry standards. The total page weight is 150 KB, and we detected 134 resource requests loading assets from 18 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 0 out of 3 JavaScript files are minified. Minifying the remaining 4 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 omaze.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 150 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for omaze.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 Size150 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests134
3rd Party Domains18
CSS Minified0/1
JS Minified0/3

omaze.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
omaze.com resolves to the IPv4 address 3.164.68.66 and also supports IPv6 (2600:9000:278c:ee00:0:4416:3740:93a1), demonstrating modern network infrastructure readiness. The domain has 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1064.awsdns-05.org, ns-1990.awsdns-56.co.uk, ns-38.awsdns-04.com, and ns-933.awsdns-52.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 omaze.com is handled by hornetsecurity.com with 4 MX records configured: mx01.hornetsecurity.com, mx02.hornetsecurity.com, and mx03.hornetsecurity.com and 1 more. 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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. 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 enabled for omaze.com, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 6 active subdomains for omaze.com: blog.omaze.com, mail.omaze.com, partners.omaze.com, shop.omaze.com, support.omaze.com, and www.omaze.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
3.164.68.66
3.164.68.92
3.164.68.81
3.164.68.118
AAAA
2600:9000:278c:ee00:0:4416:3740:93a1
NS
ns-1064.awsdns-05.org
ns-1990.awsdns-56.co.uk
ns-38.awsdns-04.com
ns-933.awsdns-52.net
MX
mx01.hornetsecurity.com
mx02.hornetsecurity.com
mx03.hornetsecurity.com
mx04.hornetsecurity.com
Email & Authentication
SPF
DMARC p=reject
DKIM
DNSSEC
MX Providerhornetsecurity.com
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (6 found)
blog.omaze.com mail.omaze.com partners.omaze.com shop.omaze.com support.omaze.com www.omaze.com

omaze.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of omaze.com contains 1,845 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 20 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 64 images. 64 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 10 internal links pointing to other pages on the same domain and 31 external links pointing to third-party websites. There are 3 external JavaScript files, 1 CSS stylesheets, and 16 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 (@OmazeUK), Instagram (@omazeuk), Youtube (@UCFtKZF8vImBVD4EI93STk3w), and Tiktok (@omaze.uk). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
1,845
Words
64
Images
0%
Alt Text Score
150
Page Size (KB)
Content Structure
H1Winlife-changingprizesHelpworld-changingcauses
H2 Tags20
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links10
External Links31
Assets & Features
JavaScript Files3
JS Minified0/3
CSS Files1
CSS Minified0/1
Iframes16
Images64
Missing Alt64
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @OmazeUKInstagram: @omazeukYoutube: @UCFtKZF8vImBVD4EI93STk3wTiktok: @omaze.uk

omaze.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for omaze.com is good at 5 characters: "Omaze". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 158 characters (acceptable): "Ever wondered how to meet a celebrity, win a trip, or get in on luxury car bidding? Omaze has an online sweepstakes for ...". 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, the meta robots directive is set to index, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to omaze.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
Omaze
https://omaze.com
Ever wondered how to meet a celebrity, win a trip, or get in on luxury car bidding? Omaze has an online sweepstakes for you. Make a donation and enter to win!
Meta Tags
TitleOmaze...
Title Length5 chars
Meta Desc Length158 chars
H1Winlife-changingprizesHelpworld-changingcauses
Languageen
Canonical
Meta Robotsindex
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconSet ✓

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

🤖 AI Summary
This section shows additional intelligence about omaze.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.