Which address received it?
A dedicated alias can point directly to the original source. If the same attack reaches multiple addresses, also check your devices, passwords, and broader data exposure.
Email exposure diagnosis
Trace where an address leaked from the first suspicious email
Spam is not just something to delete. Check which address received it, which account it imitates, and how often it appears. This can reveal whether one store is spamming you, the address was shared, or account security may be at risk.
Four-step diagnosis
Gather the facts before deciding whether to change your address
Do not reply, unsubscribe, or click suspicious emails to “test” them. These actions may confirm that the address is active.
How much does the message know?
Knowing only your address usually points to a marketing leak. Accurate details about an order, your name, or a service relationship indicate deeper exposure and call for contacting the relevant platform.
Has the frequency suddenly changed?
A shift from monthly notices to several messages a day—or a burst of reset codes—may mean the address was resold, targeted in credential stuffing, or used in login attempts.
Which important accounts are linked to the address?
If it can recover a payment, work, or long-term membership account, migrate the recovery method and strengthen verification before considering pausing the original address.
Symptoms and actions
Not every anomaly calls for the same response
Match the response to the account’s value and the evidence of exposure.
| Observed symptom | Possible cause | Priority action |
|---|---|---|
| One alias starts receiving unrelated promotions | A store shared its list or a partner is marketing to it | Pause the alias and check whether the account still needs it for recovery |
| An unsolicited verification code arrives | A mistyped address or a login attempt | Do not forward the code; check the related account’s sessions and password |
| An email accurately imitates a recent order | Order information leaked or malicious tracking | Verify through the official site, contact the store, and preserve evidence |
| Multiple aliases become suspicious at once | A risk involving your device, primary email, or passwords | Check device and account security, and enable an authenticator app |
| A few emails still arrive after pausing | Delivery was already queued | Wait for the queue to clear; contact support if it continues |
Response order
Secure the account first, then close the email entry point
If the incident involves an important account, deleting the address immediately could leave you unable to recover it.
Phase one: contain the risk
Open the account through its official website and check recent sessions, recovery addresses, and security alerts. Update reused passwords, revoke unknown sessions, and enable an authenticator app such as Google Authenticator, Microsoft Authenticator, or 1Password.
Phase two: migrate the entry point
Create a new dedicated alias, then update and verify important accounts first. Confirm that the new address receives mail before pausing or deleting the old one to avoid an interrupted migration.
Evidence checklist
Save this information when reporting an issue
Keep enough facts to investigate, but do not forward complete emails containing verification codes or sensitive tokens to unrelated people.
Headers and timestamps
Record the sender address, recipient alias, subject, arrival time, and relevant domains. Full headers can help the support team identify the true source.
Related activity in the account
Save login, order, or address-change records shown on the official account page. The absence of a matching event is also an important clue.
Actions you have taken
Note when you changed the password, revoked sessions, paused the alias, or contacted the platform. This prevents duplicate work and helps determine whether the anomaly has stopped.
Why dedicated aliases are easier to investigate
When you give your usual email address to dozens of services, it is hard to identify the source of spam. A separate entry point for each platform acts like a label on the flow of information, so you can pause just one route if it is compromised.
An alias is not a completely anonymous tool. Control the name, payment, and device information you submit, and use unique passwords and two-step verification for important accounts.
When should you contact support?
If emails continue after pausing, the status differs from what you see in the dashboard, or you cannot delete an alias you no longer need, contact support@dropfwd.com with the alias, time range, and details of the error.
Do not send passwords, verification codes, or authenticator keys. The support team does not need them and will never ask you to provide them by email.
Separate your sources
Use a dedicated entry point for your next signup
When something goes wrong, close one door without affecting your other accounts.