Question 1

Is this free?

Accepted Answer

Yes — use it at your discretion, no paywalls.

Question 2

How many aliases can I have?

Accepted Answer

As many as you want. Each one accepts up to 6 recipients (email or Telegram).

Question 3

Can I pick my own alias name?

Accepted Answer

Yes. On the create page, fill in the optional prefix field before creating — `shopping-amz@emailforward.xyz` is yours if nobody else has claimed it. Leave it blank for a random local part. Role addresses on `@emailforward.xyz` (`hello`, `admin`, `postmaster`, `privacy`, …) are reserved. On a custom domain those names are yours.

Question 4

Can I use my own domain?

Accepted Answer

Yes, free. In /manage-email → Domains, add your domain, publish the TXT record we give you, point the MX to `mail.emailforward.xyz`, and verify. Then create aliases on `*@yourdomain.com` from the same page.

Question 5

How do I connect Telegram?

Accepted Answer

Two ways: (1) In your alias setup/manage page, add a Telegram recipient — we give you a link to tap in a DM, or a /verify CODE to send in any group the bot is in. (2) From /manage-email, pair a whole inbox with /link CODE — every alias forwarding to that inbox delivers to the chat.

Question 6

Can Telegram deliver to a group?

Accepted Answer

Yes. Add @emailforwardxyz_bot to the group, then send /link CODE (inbox-wide) or /verify CODE (single alias). You can pair DMs, groups and channels side by side.

Question 7

How long do you keep my emails?

Accepted Answer

Message bodies live on our servers while the alias exists, so you can browse history or re-read in Telegram. Delete the alias and the records lose their owner.

Question 8

Can I pause an alias without losing recipients?

Accepted Answer

Yes. On the manage page, hit Pause — the alias keeps accepting mail (visible in history) but stops forwarding.

Question 9

Do I need to sign up or verify my identity?

Accepted Answer

No. Creating an alias requires only a Cloudflare Turnstile CAPTCHA — no email, no password, no personal data. Recipients confirm their own address with a one-time verification email before they ever receive a forward, so you only share aliases that actually route somewhere.

Question 10

Do you support catch-all aliases?

Accepted Answer

On @emailforward.xyz, no — each alias is its own address. On a verified custom domain you can turn catch-all on from /manage-email → Domains, so unknown local-parts (hello@, anything@, …) forward to the domain owner — email and any Telegram chats paired with that inbox.

Question 11

Can I reply from my alias?

Accepted Answer

Yes. Just hit Reply in your email client on any forwarded message — the reply goes back through us and the recipient sees the alias, never your real address. Works on aliases at `@emailforward.xyz`. Custom-domain replies need a sender signature on your domain and aren't wired up yet.

Question 12

How does deliverability work?

Accepted Answer

Forwards go out via a reputable sending infrastructure with SPF, DKIM and DMARC aligned on emailforward.xyz. We preserve the original Message-Id and set Reply-To to the original sender so your replies go to the right place.

Question 13

What happens if a recipient never verifies?

Accepted Answer

The alias is created but stays inactive until at least one recipient confirms. Inbound mail still arrives and is stored in history, but nothing is forwarded until the first confirmation.

Question 14

Can I delete an alias permanently?

Accepted Answer

Yes. From the manage page, Delete wipes the alias, its recipients, its history and any paired Telegram chats. Deletion is immediate and irreversible.

Question 15

How do I unsubscribe from a forward?

Accepted Answer

Every forwarded email carries a per-recipient unsubscribe link. Clicking it stops all forwards to that address; the alias keeps working for its other recipients.

Question 16

Is there an API?

Accepted Answer

Yes. Sign in at /manage-email → API tokens, create one, and hit `/api/v1/aliases` with an `Authorization: Bearer …` header. Full endpoint list in /docs/api. 60 writes/hour and 300 reads/hour per token.

Question 17

Is there a browser extension?

Accepted Answer

Yes — a minimal Chrome/Firefox extension that mints an alias straight into any signup form. Source lives in the repo under `browser-extension/`; load it unpacked for now (store listings pending).

Question 18

Which email providers work as recipients?

Accepted Answer

Anything that speaks SMTP — Gmail, iCloud, Proton Mail, Fastmail, custom domains. The verification link is the only gate: as long as you can receive it once, forwards go through forever after.

Question 19

What about spam filtering?

Accepted Answer

Every message to your alias goes through an automated spam filter before we forward it. Clear spam is held: it isn't forwarded to email, Telegram or webhooks, but it stays in the alias history marked "Held as spam", where you can read or download it. Borderline mail still goes through and your inbox applies its own filters on top. For senders you never want to hear from, add a blocklist rule on the alias.

Question 20

Can I use this for business email?

Accepted Answer

Technically yes, but the free tier has no SLA. For business-critical flows use a provider with redundancy.

Question 21

Is my data encrypted?

Accepted Answer

In transit: yes — TLS on all HTTPS and STARTTLS on SMTP where negotiated. At rest: no. If you need end-to-end encryption, use PGP on the sender side.

Question 22

Are there limits?

Accepted Answer

Aliases are unlimited. Forwarding by email has a daily fair-use cap: 50 emails per alias and 150 per recipient inbox (across all your aliases) in any 24 hours. Telegram and webhook deliveries don't count. Mail over the cap isn't lost: it stays in the alias history and we send you one heads-up that day. Alias creation is also throttled per IP to stop bots.

Question 23

Do you strip tracking pixels from forwarded emails?

Accepted Answer

Yes. By default, we remove 1×1 tracking pixels, tracker images from common email analytics hosts (Mailchimp, SendGrid, Mailgun, ConvertKit, HubSpot, Marketo, Klaviyo and others), and tracking query params (utm_*, mc_cid, fbclid, gclid, ck_subscriber_id and the rest) from every link before forwarding. Senders can't tell whether you opened the mail, and recipient clicks don't leak the campaign id.

Question 24

Can I use plus-addressing (alias+tag@emailforward.xyz)?

Accepted Answer

Yes. Any tag you add — e.g. newsletter-7f3a+nyt@emailforward.xyz — routes to the same alias. The tag appears in the forwarded email's X-Original-To header and in the Telegram message, so you can filter on it in Gmail (header:) or just read it at a glance in chat. Great for differentiating where the alias got breached when you've shared it with several sites.

Question 25

Can I export my data?

Accepted Answer

Yes. From /manage-email → Aliases, hit Export CSV or JSON. You get every alias tied to your inbox, with recipients and notes.

Question 26

Can I add private notes to an alias?

Accepted Answer

Yes. The manage page has a Notes card — jot down where you used it, free-text, up to 2000 chars. Visible only to whoever can open that page.

Question 27

Can I clone an alias?

Accepted Answer

Yes. On the manage page, hit Clone — pick a new prefix (or let us random one) and optionally pick a verified custom domain. Recipients are copied over; verified stays verified.

Question 28

Can I download the raw .eml of a forwarded message?

Accepted Answer

Yes. Each row in the alias history has a download button that returns the raw RFC822 bytes we received.

Frequently asked questions

Question not answered?