The digital footprint of an email
Check how many consumer platforms an email address is registered on, and which ones. You get the count and the name of each platform, with the date of the search.
Where an email is registered, in a single lookup.
Singula queries consumer platforms and returns how many recognise the address, with the name of each one. That lets your team tell an address in real use from one just created. Every response arrives with its date and its receipt.
What it confirms, and what comes next
The query confirms where the address is registered. These steps complete the rest of the file.
What it confirms
- Where the address is registered across consumer platforms, named one by one.
- The shape of the run: how many platforms were checked and how many answered yes.
- The exact date of the search, stored next to the result in the file.
The next step
- A six-digit code sent to the mailbox confirms your applicant has access to that address.
- The CURP validated at RENAPO and the RFC validated at the SAT establish the holder’s identity.
- Phone Lookup runs the same query on the phone number and returns who operates the line.
How it works
Your system asks for the search and gets a notice when it is ready.
Customer file
The search starts from the customer created in Singula, with the address stored in the file. The result stays tied to that file.
Request and receipt
Your system requests the search and receives the query receipt right away. That receipt identifies the run.
Background run
Singula queries each platform and records its answer, with a two-minute ceiling for the whole run.
Notice and result
When it finishes, your system receives an automatic notice. The full result stays stored in the customer file.
What you get back
Eight data points: the two-number summary, the platform-by-platform detail, the date and the receipt.
The address exactly as it was stored in the file when the search ran.
Example [email protected]
API field: email · stringThe number of platforms that identified the address in that run.
Example 3
API field: total_found · numberThe number of platforms queried in that run.
Example 4
API field: total_checked · numberThe full list, naming every platform that was checked in that query.
Example spotify
API field: platforms[].name · stringThe yes or no from each platform on that address in this query.
Example true
API field: platforms[].exists · booleanThe public link when the platform shares one; a good number of them keep it private.
API field: platforms[].url · string | nullThe exact date and time the search ran, stored with the result.
Example 2026-07-28T18:04:11Z
API field: checked_at · stringA unique identifier for the search, for audit and tracing.
Example 665a1b2c3d4e5f6a7b8c9d0e
API field: request_id · stringEach negative result records that the platform did not recognise the address on the date of the query.
How to read the result
Three readings of the count the query returns.
Several platforms have the address registered. The result indicates an address in real use, and stays stored in the file as backing.
This corresponds to a new address, or one with little registration across consumer platforms. The result is read together with the identity and phone checks.
None of the platforms queried has the address registered. A code sent to the mailbox or an additional document completes the review of the case.
No reading approves or declines a case on its own. Your risk policy sets the threshold.
Where it fits in your operation
Three points in your operation where the query runs.
Account signup
The query fires when the customer’s address is saved and runs while the file is assembled. The result stays stored for the review of the case.
Case review
The query adds the email footprint to an open case. The result arrives in minutes, with the receipt and date that tie it to the file.
Portfolio cleanup
The search runs customer by customer across an existing book. The result separates addresses with platform registrations from those with none.
Silent query
The search generates no emails or notices to the address being checked.
Risk profile
The footprint feeds the digital-presence category, next to the identity checks and the judicial records.
Per-query audit trail
The receipt and the full result stay tied to the customer, retrievable from the dashboard or your system.
Everything runs through the API.
Every operation on this page runs as an API call. The full field-by-field reference is in the documentation.
- Use it directly (the value in the body) or on a customer file. Same response.
curl https://api.singula.mx/app/email-lookup/customer/cus_abc123 \
-H "Authorization: Bearer sk_live_..."
→ { "status": "processing", "webhook": true }
// Webhook:
{
"email": "[email protected]",
"total_found": 7,
"total_checked": 24,
"platforms": [ { "name": "spotify", "exists": true } ]
}Frequently asked questions
No. The query returns which consumer platforms the address is registered on and how many recognise it. The mailbox is checked separately, with a code your applicant types into your form.
A set of mass-consumer platforms: social networks, music, messaging, online marketplaces and everyday services. Every response names the platforms checked and the result from each one.
No. The search always starts from the customer file. The result stays tied to that file, with a receipt and a date, and joins the person’s risk profile.
The run is capped at two minutes and usually resolves sooner. When it finishes, your system receives an automatic notice with the receipt and uses it to collect the full result.
It adds to the file as a digital-presence signal, with a receipt and a date. Identity is established separately: the CURP at RENAPO, the RFC at the SAT and the ID card against the INE Lista Nominal. The consent to process your user’s data is yours to collect, inside your own flow.
Add the email footprint to the file
A free test environment to integrate and test before going live.
Create free account