Unverified50% confidenceSolutionExact time
The core principle for defending against email enumeration attacks is response consistency: regardless of whether the email exists, the API should return the same status code, the same message text, and roughly the same response time, and should also execute equivalent placeholder logic for non-existent emails.
1
Sources
50%
Confidence
Long-term
Relevance
11/4/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedTo prevent email enumeration attacks, in the Magic Auth flow the same response should be returned regardless of whether the email exists, but emails are sent only to addresses that do exist.77% similarUnverifiedAn email enumeration attack is when an attacker infers which email addresses are already registered in a system by observing differences in the system's responses to different email addresses (such as response time, error messages, whether an email is sent, etc.).73% similarUnverifiedNonexistent email and incorrect password should return the same message to prevent attackers from probing registered emails.69% similarUnverifiedSending an email is not itself an idempotent operation; only after the email service provider accepts the request and returns a message ID can the email be confirmed as sent.68% similarUnverifiedThe email scenario is a typical case of indirect prompt injection: the attacker does not need to contact the victim and can complete the poisoning simply by sending one email.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1135006API
curl https://kongchang.com/api/v1/knowledge/claims/1135006MCP
get_claim(id=1135006)