REF: kaex (PHP) + FeezyHendrix (Python, archived 2024) ● TEST RESULT: NOT WORKING — even via residential proxy Apify Proxy: RESIDENTIAL (best) ready

Instagram Mass Account Creator — Test Harness

Deployed on ig.zipperi.com. Answers: does either reference still work? No — final signup POST is blocked (HTTP 429) on direct IP and via Apify residential proxy. Proxy fixes IP reputation but not the stale 2020 payload. Re-run below safely.

What I tested (from this server)

Identity (kaex)randomuser.me — name/email/username Identity (Feezy)feezy-local — username+num, 12-char pass, gender, birthday (no external fetch) GET /web/__mid/200 direct + via proxy GET /data/shared_data/200 direct + via proxy (csrf + device_id) POST legacy (kaex)429 direct, 429 via RESIDENTIAL — stale enc_password + old headers POST session (Feezy)429 direct, 429 via RESIDENTIAL — cookie session + plain password still rejected Apify proxy exitRESIDENTIAL works (e.g. HU/PL exit). BUYPROXIES94952 + auto also work. UNBLOCKER not used for plain curl.

Flows: kaex start.php → generateClientId → generateCsrfToken → getAccountData → createUser · Feezy creator.py → runbot/runBot → seleniumbot | requestbot(Session) → generateaccountinformation → storeusername. Selenium engine unavailable on cPanel shared (no chromedriver) — kept as reference only.

Run live tests

engine identity proxy group

Safety: single-shot only, no loops, no auto proxy scraping. Secrets stay server-side (masked outputs).

simulate count kaex file feezy file

Pick engine/identity/proxy above, then click Compare.

Feezy improvements ported

• Central lib/Config.php (amount caps, email domain, country, proxy policy).
• Feezy identity: name→username+rand(1-99), 12-char alnum password, gender + adult birthday.
• Dual engine: legacy manual-header POST vs session cookie-jar POST (tos_version=row).
• Rich storage simulated.json/csv (Name,Username,Password,Email,Gender,Birthday).
• Proxy via Apify (not sslproxies.org scrape). Selenium documented only.

Why still blocked

• Hardcoded 2020 enc_password, Chrome/79 UA, stale X-IG-App-ID.
• Missing runtime encryption, X-IG-WWW-Claim, device attestation, SMS challenge.
• Residential proxy changes exit IP (HU/PL seen) but Instagram still returns 429 empty — payload-level block, not just IP.

Files / CLI

index.php UI · api.php (diagnose/compare/simulate/dryrun/proxy_status/config/export) · lib/Tester.php · lib/ApifyProxy.php · lib/Config.php · original/ (kaex) · original-feezy/ · cli-test.php
/usr/local/cpanel/3rdparty/bin/php ~/ig.zipperi.com/cli-test.php compare --provider=feezy --proxy=1