Setup guide: Burner email plus VOIP setup for KYC airdrops

Running airdrops that require KYC creates an infrastructure problem that most guides gloss over. You need a verified email address and a working phone number for every account you operate, but using your personal Gmail and mobile number across dozens of accounts is a fast track to getting flagged, losing access to your primary inbox, and blurring the line between your real identity and your farming operations.

This guide is for operators who are participating in legitimate KYC-required airdrops using their own real identity documents, and who want dedicated, cleanly separated email and phone infrastructure to do so. everything here assumes you are presenting accurate identity information during KYC, not bypassing it. Using synthetic or stolen identities for KYC is identity fraud and outside the scope of this tutorial. if you are unsure about the legal status of multi-account participation in your jurisdiction, speak to a qualified legal professional.

By the end of this guide you will have a repeatable system for spinning up dedicated email aliases and VOIP numbers, routing them cleanly, and managing them at scale without burning your primary accounts or your time.

what you need

accounts and services - SimpleLogin (email alias layer), free tier covers 10 aliases, premium is $4/month for unlimited - AnonAddy as an alternative or secondary layer, free tier includes unlimited aliases with 10MB/month bandwidth limit - Proton Mail as your catch-all inbox, free tier available. the paid plan at $4/month lets you add custom domains - MySudo for VOIP numbers with email bundled, $0.99/month per sudo on the base plan - Hushed as an alternative VOIP provider, $1.99/month per number, 60+ country options - Google Voice if you are US-based, free but requires an existing US phone number to activate

infrastructure - a custom domain (optional but recommended at scale), roughly $10-15/year via Cloudflare Registrar or Porkbun - a password manager, Bitwarden (free) works fine - a spreadsheet or Airtable base to track alias-to-account mappings

costs at 10 accounts: approximately $5-10/month costs at 100 accounts: $20-40/month depending on which VOIP stack you choose

step by step

step 1: set up your catch-all inbox

Create a Proton Mail account that is not tied to your personal name. use something neutral like a random string or a generic handle. this inbox is not for personal use, it is a sorting layer.

Once inside Proton Mail, go to Settings > Addresses > Add address. if you are on the free plan you get one address. upgrade to Proton Mail Plus ($4/month) to add a custom domain later.

expected output: a working Proton Mail inbox with login credentials stored in Bitwarden.

if it breaks: Proton sometimes rate-limits new account creation by IP. if you hit a CAPTCHA loop, switch to a residential IP or wait 24 hours before trying again.

step 2: configure SimpleLogin for email aliases

Sign up at SimpleLogin and connect it to your Proton Mail inbox. under Settings > Mailboxes, add your Proton address as the destination. SimpleLogin will forward any alias email to Proton.

Create your first alias manually to test: Dashboard > New Custom Alias. pick a format like [email protected]. send a test email from a throwaway account and confirm it lands in Proton.

# quick test from CLI using curl (replace with your alias and a real SMTP relay)
curl --ssl-reqd \
  --url 'smtps://smtp.example.com:465' \
  --user '[email protected]:password' \
  --mail-from '[email protected]' \
  --mail-rcpt '[email protected]' \
  --upload-file test_email.txt

expected output: test email arrives in Proton within 30-60 seconds.

if it breaks: check that your Proton mailbox is verified in SimpleLogin under Settings > Mailboxes. unverified mailboxes silently drop forwards.

step 3: build your alias naming convention

Pick a naming scheme before you create more than five aliases or you will lose track of them. i use {project}-{wallet_index}@yourdomain.simplelogin.com for anything where i control the domain, or {project}-{wallet_index}-{year}@simplelogin.com on the free tier.

Log every alias in a spreadsheet with columns: alias, destination inbox, linked wallet address, project name, date created, KYC status. this mapping file is critical. at 100 accounts you cannot reconstruct this from memory.

expected output: a naming template you will follow consistently from this point forward.

if it breaks: nothing breaks here, but skipping this step will cost you hours of recovery work later.

step 4: set up VOIP numbers via MySudo or Hushed

For most non-US airdrops, MySudo’s base plan ($0.99/month) gives you a working US number capable of receiving SMS. for projects that require a local number in a specific country, Hushed has the widest country coverage I have tested personally, including UK, Germany, Canada, and Australia numbers.

Download MySudo from the App Store or Google Play. create a Sudo, assign it a number, and test by sending an SMS to it from another phone. the number shows up as a real mobile number in carrier lookup tools.

For Hushed, purchase a number from within the app. note that Hushed numbers expire if you do not use them for 30 days on the basic plan. set a calendar reminder to send a test SMS monthly.

expected output: a working VOIP number that receives SMS, confirmed with a test message.

if it breaks: some KYC providers use carrier lookup APIs and flag VOIP numbers as non-mobile. Twilio’s Lookup API documentation explains the line-type-intelligence field that providers query. if a project specifically blocks VOIP, MySudo numbers pass more checks than Hushed in my testing because they are registered on a Tier 1 carrier.

step 5: create a tracking sheet

Before you create any project-specific aliases or numbers, build the tracking sheet. i use Airtable with these fields:

Project Name | Alias Email | VOIP Number | Wallet Address | KYC Provider | KYC Status | Date Created | Notes

Export this to a local CSV weekly. do not rely solely on a cloud tool you do not control.

expected output: a populated row for every alias and number you created in steps 2-4.

if it breaks: if you forgot to log aliases before now, go to SimpleLogin Dashboard > All Aliases and export the list. MySudo and Hushed do not have export options, so reconstruct from your sent SMS history.

step 6: link alias and number to a new project account

When registering for a KYC airdrop, use one unique alias and one unique VOIP number per account registration. never reuse either across different project accounts.

Complete the email verification step first, then the SMS step. some KYC platforms like Jumio or Onfido, which are widely used in crypto projects per their published client documentation, send verification links within 5 minutes. if you do not see the email in Proton, check SimpleLogin’s activity log before assuming the alias is broken.

expected output: account registered, email verified, phone verified, all credentials logged in your tracking sheet.

if it breaks: if SMS OTP does not arrive within 3 minutes, request a resend once. if it still fails, the project may be blocking your VOIP prefix. try a Hushed number from a different country.

step 7: complete KYC with your real documents

This step is non-negotiable and non-fungible. submit accurate identity documents. KYC providers including Persona, Jumio, and Onfido use liveness detection and document verification that flags synthetic or altered documents. beyond the technical risk, submitting false documents is a criminal offence in most jurisdictions under anti-money laundering statutes, including the FATF Recommendation 10 framework that most crypto projects are legally required to comply with.

expected output: KYC status shows approved in the project dashboard.

if it breaks: if KYC is rejected, check whether the failure is document quality (resubmit with better lighting) or a region restriction (some projects block certain jurisdictions). do not attempt to work around a jurisdiction block.

step 8: archive completed accounts

Once an account has passed KYC and claimed or is eligible for its airdrop, move it to an “active” tab in your tracking sheet. update the KYC status column. if the project has a vesting schedule, set a calendar reminder for each unlock date alongside the alias email address so you receive unlock notifications.

expected output: clean tracking sheet with no ambiguous rows.

common pitfalls

reusing the same VOIP number across projects. carrier lookup tools flag numbers that appear across unrelated KYC submissions in short succession. one number per project, full stop.

not logging alias-to-wallet mappings before the alias expires. SimpleLogin’s free tier has no alias recovery if you cancel or downgrade. export your alias list monthly.

using free temporary email services for KYC. services like Guerrilla Mail or Mailinator are blocklisted by virtually every KYC provider. SimpleLogin and AnonAddy forward to a real inbox you control, which is why they work where throwaway services do not.

ignoring VOIP number expiry. Hushed basic-plan numbers expire after 30 days of inactivity. if an unlock notification goes to an expired number and the project requires re-verification, you may lose the account access window.

mixing personal and farming inboxes. never forward farming aliases to your personal Gmail or iCloud address. one cross-contamination event can link your real identity to your farming stack in ways that are hard to undo.

scaling this

10 accounts: manual management works. create aliases one at a time in SimpleLogin, buy numbers individually in MySudo.

100 accounts: you need a custom domain and SimpleLogin’s API. use the alias creation endpoint to batch-create aliases via script rather than clicking through the UI for each one. budget roughly $40/month for numbers if you are using MySudo at $0.99 each, less if you can recycle numbers across projects with long gaps between them.

import requests

SL_API_KEY = "your_api_key_here"
SUFFIX = "@yourdomain.com"

def create_alias(project_name, index):
    payload = {
        "alias_prefix": f"{project_name}-{index}",
        "signed_suffix": SUFFIX,
        "mailbox_ids": [YOUR_MAILBOX_ID]
    }
    r = requests.post(
        "https://app.simplelogin.io/api/v3/alias/custom/new",
        headers={"Authentication": SL_API_KEY},
        json=payload
    )
    return r.json()

At this scale, antidetect browser profiles become important. the infrastructure on multiaccountops.com covers the browser fingerprinting side of multi-account operations if you need a reference.

1000 accounts: you are now managing a team, not a solo operation. custom domain with catch-all routing handles the email side without per-alias overhead. for VOIP at this scale, a Twilio sub-account with programmatic number provisioning ($1/month per number in the US) becomes more cost-effective than consumer apps. you also need a proper secrets management system, not a local spreadsheet. at this scale the operational security considerations around your KYC data expand significantly, review what antidetectreview.org covers on browser and identity isolation before going further.

For a deeper look at wallet separation that pairs with this email and VOIP setup, see our guide on multi-wallet structuring for airdrop farming and the overview at the airdropfarming.org blog index.

where to go next

How to structure multiple wallets for KYC airdrops without cross-contamination, the natural next step after this email and VOIP layer is solid
Antidetect browser setup for airdrop operators, covers how to isolate browser fingerprints so your alias infrastructure is not undercut by a shared browser profile
Proxy selection guide for multi-account airdrop farming, proxyscraping.org also has practical notes on residential vs datacenter proxy tradeoffs that apply directly here

Written by Xavier Fok

disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-05-19.