Get leak statistics for an email (Public)
Leaks
Get leak statistics for an email (Public)
Public endpoint - no authentication required. Returns leak statistics for any email address including leak classification, compromised services, and risk timeline.
GET
Get leak statistics for an email (Public)
Documentation Index
Fetch the complete documentation index at: https://docs.projectdiscovery.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Get statistical information about leaks associated with any email address. This is a public endpoint that doesn’t require authentication, making it ideal for quick breach checks and self-service monitoring.Public Endpoint: No authentication required. You can check leak statistics for any email address.
Query Parameters
| Parameter | Type | Description |
|---|---|---|
email | string | Required. The email address to get leak statistics for |
Response Structure
The response provides comprehensive statistics about leaks for the specified email:Data Fields Explained
| Field | Description |
|---|---|
email | The email address these statistics apply to |
total_leaks | Total number of leaks found for this email |
leak_classification | Breakdown by leak type (personal, employee, customer) |
recent_activity | New leak discovery in recent time periods |
compromised_services | Services where this email was found in leaks |
risk_timeline | Historical trend of leak discovery |
Usage Examples
Check email breach status
No API key or authentication header is required for this endpoint.
Use Cases
Personal Breach Check
Allow users to quickly check if their email has been involved in any credential leaks.Self-Service Monitoring
Build breach notification tools that let users check their own exposure without requiring account creation.Security Awareness
Integrate into security training tools to show employees their personal exposure risk.Best Practices
- Cache results appropriately to minimize API calls
- Use this for summary data; detailed leak information requires authenticated endpoints
- Consider rate limiting when building user-facing applications
- Combine with the domain stats endpoint for comprehensive organizational monitoring
Authorizations
Response
OK