Cloaking
A stream's Cloaking section — protection level, allowed OSs, anonymizers, whitepage, and Facebook domain verification, field by field.
In the stream editor's Cloaking section, select a verification level, allowed OSs, anonymizer behavior, and a whitepage.
When the protection level is None, the entire section below is disabled (gray). Select a level first, then configure the rest.
Google Ads
When Google Ads is the stream's default pixel, darkcore forcibly disables content-differentiating cloaking for the entire stream. A regular visitor and a Google crawler receive the same route and content. Do not configure rules that show Google a different page from the user.
Protection level
The section's master switch. There are three levels:
| Level | Value | What it does |
|---|---|---|
| None | OFF (default) | Cloaking is off: all traffic sees the offer/PWA |
| Standard | FAST | GEO compliance, blacklists, user-agent bots, hosting, and anonymizer checks |
| Strict | DEEP | Adds signature, client-hint, and JS-challenge checks on top of Standard |
The level determines the signals checked before selecting the primary route. Start most launches with Standard; Strict adds deeper browser checks.
Allowed OSs
Android / iOS / Windows / macOS / Linux chips. Only traffic from selected OSs sees the PWA. An empty selection means all OSs allowed (default). For example, a mobile gambling vertical often keeps only Android and iOS.
Switches
Switches are disabled while the level is None.
| Switch | Default | What it controls |
|---|---|---|
| Allow VPN, TOR, and proxies | disabled | When disabled, VPN/TOR/proxy and data-center traffic are blocked. Enable only when the audience legitimately uses anonymizers (privacy verticals) |
| Send PageView from whitepage | disabled | Blocked traffic is included in statistics too |
Whitepage
What blocked traffic sees. Five modes:
| Mode | What it shows | Extra fields |
|---|---|---|
| Blank page | 410 Gone | — |
| Redirect to URL | Redirect to an external safe URL | Redirect URL field (required, valid URL, SSRF protection) |
| Generated | An automatically unique fantasy-app page based on vertical and language | Created automatically when selected |
| From store | Page from a real Google Play / App Store listing | Source (Google Play / App Store) plus listing URL |
| AI page | A finished page generated in AI Whitepages | Attach an existing AI page |
If the mode uses an attached entity (Generated / From store / AI), you must create it before saving or the stream will not save (“Configure a whitepage before saving”). A Strict cloak with a blank 410 whitepage looks suspicious to both moderators and bots; attach a generated or store page instead.
Whitepage generator
For a generated whitepage, set a vertical, language, and funnel brief. For AI mode, first create a page in AI Whitepages, then attach it to the stream.
Available page archetypes: product landing page, news article, creator post, magazine spread, podcast, and top list. See AI Whitepages for details.
Facebook domain verification
The fbDomainVerification field is the Meta domain-verification code. Format: Latin letters and numbers only, 8–128 characters (placeholder: abc123def456...). The code is inserted into a <meta> tag on the whitepage.
Cloaking health
Saved streams with enabled cloaking show a Cloaking health · last 24h card (updates every minute): the passed / blocked / bot share, block rate, top 3 reasons, and top 5 blocked countries.