Arbitrage chats are full of mythology about "Gmail warmup," "charging with the app open," and "no more than two signups per hour." That's not knowledge - it's forum folklore. Behind it is real mechanics worth understanding precisely.
Good news - registration ban logic is coherent. Bad news - most popular tips miss it.
Layer 1 - IP reputation
WhatsApp blocks at account level and IP level. Every server connection is logged: volume, frequency, behavioral patterns in real time. Your IP is checked against Meta internal lists and external spam databases (Spamhaus, Barracuda, etc.).
Account ban vs IP ban - different things, different symptoms. Account ban shows "this number can no longer use WhatsApp." IP ban shows nothing - messages hang on one gray tick with normal internet. If mobile data suddenly "fixed" delivery - IP problem, not account.
Datacenter IPs and known proxy ranges often auto-block. Mobile IPs (CGNAT) aren't blanket-banned - would hit legitimate users. Velocity checks still apply: abnormal SMS code request frequency from one pool is logged.
Layer 2 - Device fingerprint
At signup and use the system collects device traits: model, OS version, auth history on device, network attributes. Emulators, VMs, disposable SIMs add negative risk-score points. Fresh or factory-reset device without behavioral history reads as higher risk (profile affiliation).
Confirmed in practice: new number on a device that had prior bans - banned faster than on clean hardware.
Not officially confirmed: gyro calibration, CPU serial, "Hardware DNA" - forum guesses. Meta doesn't disclose the full signal set.
Layer 3 - Behavioral profile
Heaviest layer: send speed, intervals, reply-to-send ratio, velocity spikes (anti-spam system). In 2026: unanswered outbound count on ~30-day rolling window. 1000 sent, 50 replies - visible regardless of Gmail or hardware.
Bot pattern: equal intervals, no pauses, identical content, zero inbound. 3–8 second delays with pause every 100 sends - minimal human mimicry via unofficial API.
Meta's official line: VoIP numbers not supported. "This phone number is not allowed" for Google Voice, TextNow, typical SMS-activator disposables.
What works: paid dedicated numbers from licensed telecom with SMS/voice - often register. Cheap public activator numbers - fail or ban on first activity. Market benchmark: <10% survival on cheap virtual numbers at first bulk send (number sources).
Physical SIM from real carrier with >30 days activity - still most reliable for gray work. One SIM per account - number reuse links to prior account history.
Agency bought 15 phones and 15 SIMs for support pool. All operators in one room, registering via corporate router with static IP.
First 3 signups - fine. On 4th and 5th - SMS codes stopped. Numbers 6–15 registered after router reboot - all banned within two hours, no bulk launched. Static IP tied to shared infrastructure activity.
What failed: one public IP for all signups. Velocity checks flagged frequency. Accounts linked by IP and network.
What works: each account behind separate mobile IP, rotate before each signup. Cookie clear, new session fingerprint. 10 accounts on mobile proxy rotation - verification clean, move to organic warmup.
Replacing phone farm with anti-detect (ADSPower, Multilogin, Dolphin{anty}) + mobile proxies - viable for multi-account ops. Unique Canvas, WebGL, AudioContext per profile - but full profile isolation still critical.
Limit: WhatsApp Web via anti-detect is unofficial API - higher risk than official WABA. Inbound-reply-only tools: <2% ban rate over 12 months. Proactive cold outreach: 15–30%.
Rule: one IP - one account. Multiple accounts on one proxy - collective sanctions.
| Claim | Status |
|---|---|
| New Gmail with history raises WhatsApp trust | ❌ Unconfirmed. Gmail not needed for WhatsApp signup |
| Profile photo adds trust | ❌ Unconfirmed myth |
| App open on charger = warmup | ❌ Nonsense: keep-alive via FCM/APNs in background |
| Factory reset = new device | ⚠️ Partial. Clears local data, not necessarily hardware IDs |
| Signed up on mobile - any Wi-Fi after | ❌ IP checked continuously |
| VoIP = SIM | ❌ Not supported officially, <10% survival on bulk |
| Max 2 accounts/hour per IP | ⚠️ No confirmed number. Velocity checks yes, threshold unknown |
"Charging with WhatsApp open" - 2018 advice still copied in 2026 guides. Screen on doesn't affect background push session.
Before a new account pool: (1) each account on separate mobile IP, (2) physical or verified paid virtual numbers with history, (3) warmup from inbound and live chats, not outbound bulk. If office static IP is burned - switch to mobile before next registration wave.
Practical rule:
Registration ban is almost always IP or hardware. Bulk ban is almost always list and reply rate. Different problems, different fixes - confusing them is expensive.
