
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 publish.
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 homepage headline is "Bulletproof protection for your advertising campaigns", and 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 covers: 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.
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!"
Publishing a named architecture with a stated statistical basis is unusual in this category, and it gives you something concrete to plan streams around. The description above is Cloaking Master's own account of how the engine is built.
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 describes this as 100% protection even against the most advanced bots.
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. Following that sequence on the first campaign saves a lot of debugging later.
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, and the three methods above carry full written instructions. The Recommendations page suggests hosting white pages outside website builders when you run Facebook and Google Ads, which is worth reading before you pick a stack.
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.
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 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 worth calling out: 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, the entry tier is a complete product on its own.
Payment is cryptocurrency. The footer shows BTC, ETH, LTC, DOGE, TRX and USDT, so plan the payment side around crypto rather than card or invoice.
Payments follow the published Terms: orders are final once paid, and an active subscription runs to the end of its term, so pick the tier and stream count you want to run before you pay.
There is a trial. The homepage CTA offers "Start with a 3-day trial period!" and the FAQ adds that "you can request a trial period by contacting our support team", so message support to set one up before you subscribe.
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
Less of a 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
- · Buyers who need a documented REST API
- · Advertisers who must stay inside Google, Meta or TikTok ad policy (see below)
Things to know before you buy
Practical notes for planning a first purchase, taken from the site, the documentation and the Terms of Use.
How the subscription terms work
Terms Section 15 sets out that payments are not refunded after an order, and Section 7 states that an active subscription is not suspended or cancelled mid-term. Checkout is crypto, so it is worth picking the tier you actually want to run for the month before you subscribe.
How support works
Terms Section 16 states support is provided through the Telegram messenger when the necessary human resources are available, covers technical questions and asks you to read the documentation first. Contacts are @evilmaster777 on Telegram and support@cloaking-master.com by email.
The performance figures the vendor publishes
Cloaking Master publishes a "120 ms average response time", filtering across "over a hundred parameters", and a fake CAPTCHA it describes as "100% protection even against the most advanced bots". The full filter set behind them ships on every tier.
Both languages, one product
The site and the documentation ship in English and Russian, so a mixed EN and RU team can work from the same manual.
Trying the dashboard
The homepage Live Demo button points at demo.cloaking-master.com, which opens a sign-in screen, so evaluating the dashboard means registering an account or asking support for a look.
What stands out
You can read the whole product before you pay for it: 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 clear statement of what a cloaker can and cannot do for you.
Advertising-policy context
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, so it is worth understanding the exposure before you build a programme on it.
Cloaking Master's Terms set out where responsibility sits. 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.
Read the ad-network terms you operate under and decide what fits the programme you are running.
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, and 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.
Who Cloaking Master suits
Cloaking Master suits an operator who wants to understand a cloaker before paying for it. 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 lowest published complete product in this category, and paying more buys concurrent streams and priority support rather than a better filter, which makes it a straightforward product to start small on. The ProteX description - a discrete Bayesian classifier with a shared base model and per-stream child datasets - gives you a real model to plan against, and the per-click block tags mean you can debug a stream from the statistics view instead of a support ticket. Plan the commercial side around the published Terms: payments are not refunded after an order, an active subscription runs to the end of its term, and checkout is crypto, so start on the tier you actually want to run and ask support about the trial first. And be clear-eyed about the category: cloaking sits outside the advertising policies of every major network, and these Terms leave that exposure with the advertiser.
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). Figures such as a 120 ms average response time, protection across "over a hundred parameters" and "100% protection" from the fake CAPTCHA filter are published by the vendor and reported here as published rather than as measured by us. Cloaking sits outside the advertising policies of Google, Meta, TikTok and other major networks, 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".