This can take up to 60 seconds. Please wait...
Domain Summary
What is the traffic rank for Whacka.app?
What percent of global Internet users visit Whacka.app?
How many people visit Whacka.app each day?
Which countries does Whacka.app receive most of its visitors from?
How much Whacka.app can earn?
What is Whacka.app estimated value?
What IP addresses does Whacka.app resolve to?
whacka.app Profile
What technologies does whacka.app use?
These are the technologies used at whacka.app. whacka.app has a total of 9 technologies installed in 8 different categories.
whacka.app Traffic Analysis
Whacka.app is ranked #146,261 in the world. This website is viewed by an estimated 10.3K visitors daily, generating a total of 55.3K pageviews. This equates to about 311.2K monthly visitors. Whacka.app traffic has increased by 125.34% compared to last month.
- Daily Unique Visitors
- 10,270
- Monthly Visits
- 311,181
- Pages per Visit
- 5.38
- Daily Pageviews
- 55,282
- Avg. Visit Duration
- 04:52
- Bounce Rate
- 38.28%
- Global Reach
- 0.000171%
- Monthly Visits (SEMrush)
- 435,333
- Monthly Unique Visitors (SEMrush)
- 158,517
- Monthly Visits (SimilarWeb)
- 305,056
- HypeRank
- 146,261
- SEMrush Rank
- 1,505,994
- SimilarWeb Rank
- 117,204
*All traffic values are estimates only.
Traffic Sources
Desktop vs Mobile
Monthly Visits
Visitors by Country
| Country | Users % |
|---|---|
| Egypt | 47.30% |
| Saudi Arabia | 12.51% |
| Morocco | 9.75% |
| Algeria | 9.62% |
| United States | 7.19% |
whacka.app SEMrush Overview
SEMrush is a complete online advertising and marketing platform that gives a wide variety of tools and features to help businesses and marketers improve their online visibility and optimize their digital marketing strategies.
- Domain
- whacka.app
- RankBased on keywords, cost and organic traffic
- 1,505,994
- Organic KeywordsKeywords in top 20 Google SERP
- 24
- Organic TrafficVisitors coming from top 20 search results
- 621
- Organic CostEquivalent Google Ads spend for the same traffic
- $15.00
Backlinks Report
Whacka.app has a total of 50,467 backlinks from 492 referring domains and most of them comes from United States.
Backlinks by Country
| Country | Domains |
|---|---|
| United States | 78 |
| China | 45 |
| Moldova | 17 |
| Singapore | 9 |
| Hong Kong | 7 |
Backlinks by TLDs
| TLD | Domains |
|---|---|
| .com | 239 |
| .ai | 30 |
| .shop | 27 |
| .edu | 0 |
| .gov | 0 |
Search Engine Indexes
Search engine indexes are huge databases of web pages that search engines like Google and Baidu use to retrieve relevant results when users search. These indexes are built by crawling and indexing pages from across the web.
Revenue Report
whacka.app would generate approximately $32.3 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $1K and annual gross revenue of approximately $11.8K. Based on these figures, the site's net worth is estimated at around $29.5K.
How much would whacka.app make?
How much is whacka.app worth?
*All earnings values are estimates only.
Daily Earning by Country
| Country | Pageviews | Earning |
|---|---|---|
| United States | 3,974 | $15.74 |
| Egypt | 26,150 | $3.48 |
| Morocco | 5,392 | $3.17 |
| Saudi Arabia | 6,915 | $3.11 |
| Algeria | 5,320 | $2.48 |
Daily Revenue Loss by Country
| Country | Blocked | Lost |
|---|---|---|
| United States | 715 | $3.45 |
| Saudi Arabia | 1,452 | $0.83 |
| Egypt | 1,308 | $0.18 |
| Algeria | 266 | $0.13 |
| Morocco | 108 | $0.06 |
Impact of Ad Blockers
Ad Experience Report
Summary of the ad and abusive experience ratings Google assigns to whacka.app, per platform.
Mobile Summary
- Root Domain
- whacka.app
- Ad FilteringChrome is not filtering ads on your site.
- Off
- StatusReviewed against the Better Ads Standards
- Not reviewed
Desktop Summary
- Root Domain
- whacka.app
- Ad FilteringChrome is not filtering ads on your site.
- Off
- StatusReviewed against the Better Ads Standards
- Not reviewed
Abusive Experience
- Root Domain
- whacka.app
- EnforcementChrome is not preventing your site from opening new windows or tabs.
- Off
- StatusReviewed for abusive experiences
- Not reviewed
Where is whacka.app hosted?
Whacka.app is behind Cloudflare (CDN and security proxy). Visitors connect to Cloudflare's shared IP addresses, which answer from the nearest Cloudflare data center, so the real server location is hidden.
- Server IP
- 172.66.42.230
- ASN
- AS13335
- ISP
- Cloudflare, Inc. CDN / proxy
- Server Location
- Hidden behind Cloudflare
Other sites using the same Cloudflare IP 172.66.42.230
How fast does whacka.app load?
The average loading time of whacka.app is 184 ms. The Desktop speed index is 89 and mobile speed index is 0.
Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report. We are showing the 90th percentile of FCP and the 95th percentile of FID.
All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report over the last 30 days. To view suggestions tailored to each page, analyze individual page URLs.
Does whacka.app use compression?
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on whacka.app are reduced by 86%.
Saved 90.7 KB off the original size
Google Safe Browsing
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
WOT MyWot.com Reputation Ratings
MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
- Status
- SAFE
SSL Checker SSL Certificate Verify
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. whacka.app supports HTTPS.
Organization:
Location:
Issuer: YE1
Valid from: Oct 27 10:58:08 2026 GMT
Valid until: Jan 25 10:58:07 2027 GMT
Authority: CA:FALSE
Keysize:
Organization: Let's Encrypt
Location: US
Issuer: Root YE
Valid from: Sep 3 00:00:00 2025 GMT
Valid until: Sep 2 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize:
Organization: ISRG
Location: US
Issuer: ISRG Root X2
Valid from: May 13 00:00:00 2026 GMT
Valid until: Sep 2 23:59:59 2032 GMT
Authority: CA:TRUE
Keysize:
Organization: Internet Security Research Group
Location: US
Issuer: ISRG Root X1
Valid from: May 13 00:00:00 2026 GMT
Valid until: Sep 2 23:59:59 2032 GMT
Authority: CA:TRUE
Keysize:
Security Headers
HTTP security headers tell browsers how to protect visitors: force HTTPS, block clickjacking and limit what scripts can do. whacka.app sends 3 of the 6 recommended security headers, and its SSL certificate is issued by Let's Encrypt.
- Strict-Transport-Security
- present
- Content-Security-Policy
- missing
- X-Frame-Options
- missing
- X-Content-Type-Options
- present
- Referrer-Policy
- present
- Permissions-Policy
- missing
- SSL issuer
- Let's Encrypt
- SSL expires
- 2027-01-25 in 85 days
Email Security
SPF, DKIM and DMARC are DNS records that prove which servers may send email for a domain and tell receivers what to do with forged messages. whacka.app has SPF and an enforced DMARC policy, which protects it against email spoofing.
- Email provider
- Google Workspace
- SPF
- present
- DMARC
- quarantine
- DKIM
- found
- DNSSEC
- not signed
v=spf1 include:dc-aa8e722993._spfm.whacka.app ~all
AI Crawlers
Websites use robots.txt to allow or block AI crawlers that collect content for training and AI search. whacka.app does not block any known AI crawler.
- llms.txt
- not found
Verify HTTP/2 & HTTP/3 Support
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.
Http Header
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.
date: Sat, 31 Oct 2026 01:17:03 GMT
content-type: text/html; charset=utf-8
server: cloudflare
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin
set-cookie: whacka-locale=en; Path=/; Expires=Sun, 31 Oct 2027 01:17:02 GMT; Max-Age=31536000; Secure; SameSite=lax
x-whacka-locale: en
vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
link: </_next/static/media/1a4aa50920b5315c-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/26d0ba92e140f0dc-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/27834908180db20f-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/4bbca553a70e7419-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/4d4e07637fe6030d-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/78fec81b34c4a365-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/7d9a813ffbcaadee-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/bdfad1964dd7aebe-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/cb6758d0c09ff285-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </landing-v2/hero/poster-team_work.jpg>; rel=preload; as="image"; fetchpriority="high", </landing-v2/capability/bookings.avif>; rel=preload; as="image"
cache-control: private, no-cache, no-store, max-age=0, must-revalidate
cache-control: no-cache, no-store, must-revalidate
strict-transport-security: max-age=2592000; includeSubDomains
pragma: no-cache
expires: 0
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=NGZ2aMU2Sgbr1hQoWPplyTrs4Uu7caBlEb0XzBOj1CQQzrHEOm62H5T8WL8bEY8mCTQCWHTtJgl9736LwBosCRbXLNEuit9tLrpyO0fPOih%2FAhlmpVaHJhmpDkLFYjSlUWTkdKxzVOc%3D"}]}
cf-cache-status: DYNAMIC
content-encoding: br
cf-ray: a52ed15d0a27856c-FRA
alt-svc: h3=":443"; ma=86400
DNS Lookup
DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
| Type | IP | Target / TXT | TTL |
|---|---|---|---|
| HINFO | 3600 |


