If something is wrong

Connecting a domain takes from 30 minutes to 72 hours — that is the DNS refresh speed at the registrar, not the panel’s. Check:

• The domain’s DNS has an A record for the domain root pointing to the IP the wizard showed (it is also visible when adding the domain).
• There is only one record: old A records pointing to another IP are better deleted.
• You can check whether DNS has updated on dnschecker.org.

If the check is fine but it does not open for you — your computer still has old DNS cached. Open the site from mobile internet.

The panel checks the domain itself and updates the status as soon as the record becomes visible. If more than 72 hours have passed, the record was most likely entered wrongly: check the IP, that there are no typos in the domain and that the record was added at the registrar where you manage DNS (sometimes a domain is bought in one place while the DNS servers point to another).

This is how a domain behind the Cloudflare proxy is shown: the real IP is hidden, but the record is in place. This is normal, and the site opens. More in the Adding a domain section.

The domain does not resolve or the registrar put it into a lock status (hold, redemption, pending delete). The most common cause is an overdue domain payment or a complaint against it. Go to the registrar’s account and look at the domain status; without the registrar’s decision the site will not work.

Google Safe Browsing flagged the site as dangerous — Chrome shows visitors a red warning. You can confirm and request a review in Google Search Console (the security issues section); for that the domain must be added to Search Console — see Google indexing. While the flag is up, it is better not to send traffic to this domain.

Cloudflare shows visitors a phishing page. Request a review in the Cloudflare dashboard where the domain is connected. If the domain is not behind Cloudflare, the cloud will be gray — that is normal, there is nothing to check there.

The site did not respond during the check or returned a server error. First open the domain yourself. If it opens — it may have been a short glitch, and the problem will disappear at the next check. If not — see the “Domain and site” block above.

• The domain must be connected and open. Check the status in the “Domains” tab.
• Shop data reaches the panel about once a minute, and the by-day chart of a new domain starts filling from the next day.
• Visitors are counted as unique: if you open the site yourself, that is one visit.

• Only completed requests count toward the share. Requests that are “Queued”, “Awaiting trade” and “On hold” are not counted yet.
• Requests that came to a domain before it was added to the panel are not accrued.
• The accrual appears after the next sync — about a minute.

What each number means — in Statistics: what the numbers mean.

Steam protects CS2 trades, so the share for such items becomes available after about 8 days. Until then it shows as “On hold” in the “Payouts” tab. Dota 2, Rust and TF2 have no hold.

Payouts are processed manually, there is no fixed time. Statuses in the history: “Pending” — the request is accepted and awaits processing, “Paid” — sent to the wallet, “Rejected” — the withdrawal was not made. Double-check the address and network: money cannot be returned from a wrong address. If a request hangs as “Pending” longer than usual, write to the team in the bot.

This is normal: volume is the sales size in settlement value (60% of the Steam market price), and the share is your percentage of it. See Share and tiers.

Since October 18, 2026 completed requests are kept in the panel permanently. Requests the shop deleted earlier cannot be restored, so for an old period the tiles may show less than has accumulated in accruals. For money, rely on the big “Your share accrued” number and the balance in “Payouts”.

• The code comes to the bot @ZFlow_tbot — it must be started (“Start” pressed) and not blocked.
• The code is valid for 5 minutes, with 5 attempts to enter it. If time ran out, just sign in again — a new code will arrive.

After 5 wrong passwords in a row, login is closed for 15 seconds, and each following error doubles the pause (up to an hour). Wait the stated time and enter the password without typos. The error counter resets on a successful login or if there were no errors for an hour.

If Telegram is linked, you can only sign in with a code from the bot. Write to the ZFlow team in the bot from another account or through the contacts in the documentation header — they will help restore access.

Login is closed and the domains go to the owner. Ask the ZFlow team in the bot about the reasons and the unblocking procedure.