1 send = 1 credit5 free on open

Spoofed mail that lands in the inbox

Pick a template, set the From address, send from your own SMTP through Telegram. DKIM-signed, header-forged, 1 send = 1 credit.

The sender. Template, From, target, your SMTP — one send, one credit.

Templates for every mark. Banks, wallets, accounts — each matched to the real thing.

Account alerts

Google security alerts, Facebook login checks, Apple ID verifications — the mails nobody questions.

Bank holds

Chase, HSBC, Wells Fargo — unusual-activity mails with a deadline that forces the click.

From your SMTP, through the forge. Three steps, every send.

Pick the template

Account, bank or wallet. The subject, headers and layout match the real mail.

Set the From

Any address on any pattern — noreply@google.com.id, no.reply@chase.com.verify.

Send from your SMTP

Your own relay, DKIM-signed with your key. The headers carry the mask.

Credits, not subscriptions. 1 send = 1 credit. Redeem card codes in the app.

Redeem a card

Every card code works once and adds its credits to your account instantly.

Your last sends

Every send is logged with its status — inbox hits and bounces, both visible.

Who runs it. Senders, resellers, testers.

  • Phishers
  • Carders
  • Resellers
  • Red Teams
  • Mail Testers
  • Drop Shops
  • Scampages
  • OTP Shops
  • Bank Logs
  • Spam crews

Questions senders ask.

Where does the mail send from?

Your own SMTP relay — you bring the host, port and login. The forge signs it with your DKIM key and forges the headers.

What lands in the inbox?

Google-pattern mail on a gmail.com.id From lands where SPF allows it. Your DKIM on your domain does the rest.

How do credits work?

One send costs one credit, refunded if the send fails. New users start with 5. Card codes add more.

Do you sell credits?

The admin mints card codes on request. Ping the bot owner to buy.