
Cloaking Master Review 2026
Cloud cloaking on the ProteX engine · PHP, CMS and JavaScript integration · from $99/mo, crypto checkout
Cloaking Master is a cloud traffic-filtering and cloaking service aimed at media buyers and affiliate teams. Its own documentation calls it "a powerful and versatile cloud service designed to protect advertising campaigns, such as affiliate offers, landing pages, file downloads, and other content from unwanted traffic, including: various types of bots, ad moderators, antivirus companies, spy services, and other types of suspicious or irrelevant visitors." Every inbound click is checked before the visitor lands, and the service routes real users to the offer page while everyone else gets the white page. The decision engine is the vendor's proprietary ProteX technology, which the vendor describes as a self-learning machine-learning model doing deep fingerprint analysis at both the PHP and JavaScript layers across more than a hundred parameters. Three plans are published openly at $99, $199 and $399 per month, and the full documentation is readable without an account. This review is based on what the site, its documentation and its Terms of Use actually state; where a number is a vendor claim we say so rather than repeat it as fact.
At a glance
Counts taken from the vendor's own homepage feature list and the public statistics reference in its documentation. Pricing is published openly on the homepage. Figures verified 28.07.2026.
What Cloaking Master actually does
A cloaker sits in front of your landing page and decides, per request, which of two pages a visitor sees. Cloaking Master's documentation states the flow plainly: "Visitors (traffic of any type - ads, bots, moderators, organizations, etc.) visit your site, and before they land on the page, Cloaking Master performs over a hundred checks on each click and determines whether the visitor is relevant or unwanted. Relevant visitors are directed to your real income-generating content (Offer page), while unwanted visitors are shown an alternative legitimate page (White page)."
The marketing framing is more aggressive - the homepage headline is "Bulletproof protection for your advertising campaigns" - but the mechanism underneath is the standard two-page split, executed as a hosted cloud service rather than something you run yourself. The vendor names the ad platforms it says it protects against: Google, Bing, YouTube, Yahoo, Yandex, Facebook, Instagram, TikTok, X (Twitter), VK, LinkedIn, Reddit and Snapchat.
Named automation targets
The homepage states ProteX "detects and blocks even the most advanced bots based on headless browsers" and names these specifically.
Scanner protection
Beyond ad moderators, the vendor lists antivirus software, spy services, antifraud systems, brand-safety tools and competitor checks as things the filter is meant to keep off the offer page. No detection rates are published for any of these categories.
ProteX, in the vendor's own words
ProteX is the trademarked name for the decision engine, and unlike most vendors in this category Cloaking Master publishes a description of how it is supposed to work. From the documentation: "The foundation of ProteX is a self-learning model built on the principles of a discrete Bayesian classifier. It can be thought of as a system with a single central brain - a common dataset containing basic patterns and rules - and numerous local specializations, or child datasets, each individual to a specific stream."
The practical implication of that architecture, as the vendor states it, is that "each stream creates its own context and accumulated experience, enabling the system to adapt to its unique characteristics". That is also why the Recommendations page insists on one stream per ad campaign: mixing several campaigns into a single stream muddies the per-stream dataset, and the docs say outright "We cannot review your traffic if you mix multiple campaigns in one stream!"
A named architecture with a stated statistical basis is more than most competitors disclose, and it is worth crediting. It is still a vendor description of a closed system: there is no published training-data description, no accuracy figure and no third-party evaluation. Treat it as design intent, not as a measured result.
The filter parameters
Nineteen parameters are listed on the homepage as what ProteX evaluates. Each is configurable as a filter object that you attach to one or more streams, so the same rule set can be reused across campaigns.
The JavaScript layer
The documentation is unusually specific about what happens once a visitor passes the server-side checks: "A white page is loaded, hidden from view under a white background and a loader, and only after successfully passing all JS filters will the content be redirected or replaced with the offer page. If the visitor fails the JS check, the white background and loader are hidden, and they remain on the white page." These are the individual JS-layer checks:
If the IP exposed through WebRTC does not match the IP of the request, the visitor is blocked.
Requires the device to report a battery. Devices without one are blocked.
Requires touch input. The docs note this alone filters out many desktop-browser moderators and antivirus bots.
A checkbox overlay on the white page. Only after a click does the content swap to the offer page. The vendor calls this "100% protection"; that is a marketing claim, not a measured figure.
Allow or block by width and height thresholds in pixels.
Server-side blocking defaults
The docs also flag which server-side toggles the vendor recommends leaving on: Block Server/Host (all requests from servers and hosting ranges) and Block without ISP (requests with no identified provider). Block IPv6 is explicitly not recommended unless you need it. Country and language filters allow everything when left empty.
Streams, modes and how content is served
Streams
A stream is the unit of work, defined in the docs as "a traffic channel that can be managed as a whole, similar to a campaign in an ad network." Your plan is priced by how many streams can be active at once, not by clicks or bandwidth.
Five stream modes
Live filtering (Cloaking), a Moderation mode that serves the white page to everyone while a campaign is under review, an offer-page-only mode and a white-page-only mode that both keep statistics on, and a fully disabled mode with filtering and statistics off.
Worth reading twice: the docs warn that while a stream is in Moderation mode you should "not visit the stream link ... or you will be automatically blocked", and the recommended workflow is to submit the ad campaign in Moderation mode and only switch to Cloaking once it is approved and before traffic starts. Getting that sequence wrong is a self-inflicted failure mode, not a product fault, but it is easy to trip over on the first campaign.
Four content display methods
Lazy loading
Serves a local file on the same domain as the PHP integration. The docs call this "the safest" method and strongly recommend it wherever technically possible.
Redirect
Redirect to another domain. Documented as offer-page only.
Iframe
Renders a page inside an iframe without changing the address bar.
Proxy
Smart HTTP proxying that renders an external site on your domain and preserves its navigation. The docs concede that "in some cases, the result may be broken or distorted."
Integration
The documentation lists three integration methods, and notes that "Integration files do not contain stream settings", so changing a filter or mode applies in real time without re-uploading anything.
- PHP. Rename your root
index.htmltosite.html, download theirindex.php, upload it to your web root and point the offer page atsite.html. Described as universal and suitable for any traffic source. - WordPress and other CMS. Upload
cloaking.phpto the web root and add a singlerequireline at the top of the CMSindex.php. - JavaScript. Add a stylesheet link and a script tag, both keyed to your stream key, before the closing head tag of your white page.
The marketing pages additionally name Shopify, Wix, Tilda, Weblium and Keitaro as supported environments. The docs navigation has a Shopify entry and a site-builders entry, but at the time of writing only the three methods above have written instructions. Note also that the Recommendations page advises against using website builders for white pages with Facebook and Google Ads, which sits awkwardly beside the marketing list.
Statistics: every block is labelled
This is one of the more practically useful parts of the product. Cloaking Master logs every click and tags each blocked visit with the specific reason. The public documentation lists the full tag set, so you can debug a filter without opening a support ticket:
Two of those tags matter more than the rest when you are diagnosing traffic: System means ProteX itself made the call (no further reason given), and Moderation means the IP is on the vendor's moderator blacklist. The rest map one-to-one onto rules you set yourself.
Real-time statistics
Per-click detail, traffic source, quality and the filtered-traffic ratio, in real time per the vendor.
Postback tracking
Built-in conversion tracking via postback, which the vendor positions as removing the need for a third-party tracker for conversion data.
AI white page generator
Generates white pages the vendor says are built to comply with Google Ads, Facebook and TikTok requirements, including terms of use, privacy policy and cookie pages.
Plans and pricing
Cloaking Master publishes full public pricing on its homepage. Three monthly tiers, separated only by active-stream count and support level. Figures verified 28.07.2026.
Identical on every tier
That is unusual and worth calling out as a positive: the entire filter set ships on the $99 plan. You are not paying more for better detection, you are paying for more concurrent streams. For a solo buyer running a handful of campaigns, that makes the entry tier a genuinely complete product rather than a crippled teaser.
Payment is cryptocurrency only. The footer shows BTC, ETH, LTC, DOGE, TRX and USDT. There is no card, PayPal or bank-transfer option and no invoicing, so teams that need VAT paperwork are not the target buyer. Crypto-first checkout is the norm across cloaking vendors rather than an outlier.
The Terms are strict on money. Section 15 is titled "No Refund Policy" and states the company "provides intangible, non-revocable services and therefore does not offer refunds after payment for an order." Section 7 adds that "An active Subscription cannot be suspended or canceled." Section 14 states that discounts and promo codes are "a privilege for the user, not a right" and may be refused without explanation.
The trial story is inconsistent. The homepage CTA says "Start with a 3-day trial period!", the FAQ says "you can request a trial period by contacting our support team", and the page meta description advertises a "5-day free trial". Three different answers on the same page. Ask support what you are actually getting before you assume.
Who it fits
A reasonable fit for
- · Solo buyers and small teams who want the full filter set at the lowest published entry price in this category
- · Operators who want to read the manual before paying - the documentation is genuinely public and detailed
- · Teams running WordPress or plain PHP landing pages, where integration is a file upload and one line of code
- · Buyers who want per-click block reasons visible in statistics rather than an opaque allowed/blocked counter
- · Russian-speaking teams: the site and the vendor materials ship in EN and RU
A poor fit for
- · Any company that needs invoices, VAT paperwork or card payment
- · Anyone who needs the ability to cancel or refund a subscription mid-term
- · Teams with a data-protection review requirement - no privacy policy is published
- · Buyers who need a documented REST API; none is published in the docs
- · Advertisers who must stay inside Google, Meta or TikTok ad policy (see below)
Things to know before you buy
Stated plainly, and measured against how this category actually operates rather than against enterprise SaaS norms. None of these are dealbreakers on their own; together they define who this suits.
No privacy policy is published
The footer lists Documentation and Terms of Use. The Privacy Policy link exists in the page source but is commented out, so it renders as dead text rather than a link. For a service that processes visitor IPs, user agents, WebRTC data and device fingerprints at scale, the absence of any published privacy document is the single most notable gap on the site.
The published price contradicts the site’s own structured data
The visible pricing table lists Premium at $399/month with no stream limit. The SoftwareApplication JSON-LD embedded in the same page lists Premium at $299.00 with "30 Active stream". One of those is stale. Confirm the current Premium terms in writing before paying, and treat $399 unlimited as the figure the vendor displays to buyers.
Absolute no-refund policy, no cancellation
Terms Section 15 rules out refunds after payment outright. Section 7 states an active subscription cannot be suspended or cancelled. Combined with crypto-only checkout, there is no chargeback path either. Start on the cheapest tier or the trial, not on Premium.
Support is Telegram, and framed as a privilege
Terms Section 16 states support is provided "only through the Telegram messenger and only when necessary human resources are available", limits it to technical questions, requires you to read the documentation first, and reserves the right to refuse support at the company’s discretion. Telegram-only support is normal in this category; the explicit framing is unusually blunt. Contacts are @evilmaster777 for support and support@cloaking-master.com by email.
Performance and protection numbers are vendor-stated
A "120 ms average response time", "over a hundred parameters", and a fake CAPTCHA that "guarantees 100% protection even against the most advanced bots" are all published without methodology or third-party audit. The 100% claim in particular is not a measurable property of any filter. Read these as positioning, not measurement. This is standard across cloaking vendors, none of whom publish audited detection rates.
A competitor’s name is still in the documentation
The Recommendations page warns against naming a file index.html because it may take priority "causing the Adspect filter page to be opened instead of the actual content". Adspect is a different vendor. That is a copy-paste artifact in the manual, harmless in itself, but it means the recommendations page is not entirely original writing.
Untranslated Russian on the English site
The English homepage integration list ends with "Tilda, Wix и т.п.", and the English documentation sidebar carries Russian labels for two sections. Small, but a reminder that EN is a translation layer over an RU-first product rather than a native build.
Young domain, older stated founding date
cloaking-master.com was registered on 31.01.2025 through Cloudflare. The site’s Organization schema declares a 2024 founding date and the documentation footer reads "© 2024-". The vendor may well have operated before registering this domain, but the public paper trail starts in 2025. There is no public status page or SLA.
The "Live Demo" link is a sign-in page
The homepage Live Demo button points at demo.cloaking-master.com, which redirects to a sign-in screen. No demo credentials are published on the site, so evaluating the dashboard means registering or asking support.
Credit where it is due
Most vendors in this category hide their documentation behind a login, which makes independent assessment impossible before payment. Cloaking Master does the opposite: the full manual is public at docs.cloaking-master.com, including the ProteX architecture description, every filter parameter, the complete statistics tag reference and the integration code. Nearly every technical fact in this review came from reading it without an account.
The Recommendations page goes further than product docs usually do, including an unusually frank closing note that no cloaker can save a careless operator: "We can guarantee solid protection from routine checks, but no service can protect you from a special investigation into possible violations of rules." That is a more honest statement of the limits of cloaking than most of this industry publishes.
The category risk, stated plainly
Cloaking exists to show ad-network reviewers different content than real users see. That is a direct violation of Google, Meta and TikTok advertising policies regardless of what is being promoted, and it can cost you accounts, spend and business relationships. Any review that does not say this out loud is not being useful.
Cloaking Master's own Terms push consequences onto the customer. Section 2 forbids using the service for criminal or illegal purposes, money laundering, spam distribution and similar activity, and Section 9 requires you to indemnify the company against claims arising from your use. Section 5 states that nothing the company or its staff says should be treated as legal or professional advice. Section 8 makes access "a privilege, not a right", terminable without notice.
The vendor's own homepage FAQ lists "Complying with advertising platform requirements" among the uses of cloaking. We would not characterise it that way: cloaking is a way of managing what reviewers see, and the platforms whose requirements are at issue explicitly prohibit it.
PROXIES.SX lists this partner as a review, not an endorsement of policy evasion. Read the ad-network terms you operate under and decide for yourself.
Using Cloaking Master with PROXIES.SX mobile proxies
These two products sit on opposite sides of the connection, which is worth being precise about. Cloaking Master classifies inbound visitors arriving at a landing page you control. PROXIES.SX supplies outbound 4G/5G mobile and residential IPs for the work you do before traffic ever reaches that page. Neither replaces the other, and neither is a way around the other.
Cloaking Master
Landing layer - decides per click whether a visitor sees the white page or the offer page, and tags the reason in statistics.
PROXIES.SX
Network layer - 4G/5G mobile carrier and residential IPs for account work, geo checks and QA. Endpoints are free; you pay per GB from $4/GB down to $2.40/GB at volume, and GB never expire.
One thing to plan for
Cloaking Master ships an explicit VPN/Proxy filter, a Block Server/Host toggle the vendor recommends leaving enabled, and a Block without ISP toggle. That means your own proxied QA visits can legitimately be classified as filtered traffic when you check how a funnel renders from another country. Before concluding a page is broken, open the statistics view and read the tag on your own click - VPN/Proxy, Host or No ISP tells you the filter did its job, not that the page failed. Use the IP allow lists to carve out your own test addresses. We are not claiming our IPs pass any given cloaker; we are saying test with the decision log open.
A second, subtler one
Several of the JavaScript checks are device-shape checks: touchscreen present, battery present, and screen-size thresholds. A desktop QA browser tunnelled through a mobile IP still looks like a desktop to those filters. If you are validating a mobile campaign, match the device profile as well as the IP, or your test click will be blocked for reasons that have nothing to do with the network.
Verdict
Cloaking Master's real differentiator is not ProteX, it is transparency about the product. The full manual is public, the filter parameters are enumerated, the block-reason tags are documented one by one, the integration code is printed, and all three prices are on the homepage. At $99/month with the complete filter set included, the entry tier is the cheapest complete product we have reviewed in this category, and paying more only buys concurrent streams and priority support rather than better detection. The ProteX description - a discrete Bayesian classifier with a shared base model and per-stream child datasets - is more architectural detail than most competitors disclose, though it remains a vendor description of a closed system with no published accuracy figures. Against that: no privacy policy is published at all, which is a real gap for a service that fingerprints visitors; the Terms combine an absolute no-refund clause with a no-cancellation clause and crypto-only payment, so there is no way back out of a purchase; and the site contradicts itself on both Premium pricing and trial length, which is the kind of sloppiness that makes you want everything confirmed in writing before you pay. The manual also still carries a competitor's product name in one recommendation. Be clear-eyed about the category as well: cloaking violates the advertising policies of every major network, and these Terms leave those consequences with you.
Related reviews
Cloaking Master facts in this review reflect the vendor's public site at cloaking-master.com, its public documentation at docs.cloaking-master.com and its Terms of Use (last updated 12.01.2026), all read on 28.07.2026, plus a vendor-supplied product brief. Filter parameters, stream modes, content display methods, integration steps and the statistics tag list are taken verbatim from the vendor's own documentation. Pricing is published publicly on the homepage - Basic $99/mo (3 streams), Standard $199/mo (10 streams), Premium $399/mo (unlimited streams) - and we note that the page's own structured data lists Premium at $299 for 30 streams, a discrepancy we could not resolve from public sources. Claims such as a 120 ms average response time, protection across "over a hundred parameters" and "100% protection" from the fake CAPTCHA filter are vendor statements we could not independently verify and are labelled as such rather than repeated as fact. The vendor's Organization schema links a Trustpilot profile; that page could not be loaded from our test machine, so we make no claim about its contents. Cloaking violates the advertising policies of Google, Meta, TikTok and other major networks; this review is an assessment, not an endorsement of policy evasion, and readers are responsible for complying with the terms of any platform they advertise on. Outbound links to cloaking-master.com, its documentation and Telegram use rel="nofollow sponsored noopener noreferrer".