Digital footprint
always onThe original service. One request tells you which platforms an email address, phone number or username is registered with, plus breach history and public web mentions.
Returns
- Platform registrations
- Breach records
- Public web mentions
Email check
add-onMailbox-level facts established over SMTP rather than guessed from the domain, plus how long the domain has been registered.
Returns
- Deliverable
- Disposable
- Consumer webmail
- Catch-all domain
- Domain age
Phone check
add-onCarrier and line type for a number, separating a genuine mobile line from the app-minted virtual numbers used to get past signup forms.
Returns
- Valid
- Carrier
- Line type
- VOIP detection
- Fixed vs non-fixed VOIP
IP check
add-onA risk score for an IP address with VPN, proxy, Tor and datacenter flags, the operator name where it can be identified, and network ownership with location.
Returns
- Risk score
- VPN / proxy / Tor
- Datacenter
- Network owner
- Location
Risk scoring & rules
add-onEvery email, phone and IP module returns a 0-100 risk score, and the request gets an overall score that is the total of the named signals that fired, capped at 100. Tune any default rule for your own traffic or write your own.
Returns
- Overall score
- Per-module scores
- Named signals
- Editable default rules
- Custom rules
Combining them
The digital footprint runs on every lookup. Add the others by naming them in checks, and send the identifiers they need in the same request.
POST /v2/lookup?wait=true
{
"email": "someone@example.com",
"phone": "+14155552671",
"ip": "8.8.8.8",
"checks": {
"footprint": { "early": true, "hits": 3, "maxWaitMs": 2500 },
"email": true,
"phone": true,
"ip": true,
"breaches": true,
"riskSignals": true
}
}
That is every key: the footprint with an early answer, email, phone and IP intelligence, breaches (send false to skip them) and the named signals behind each risk score. Don't know what an input is? Send it as query and it is detected for you. Every option is on the checks page.
Add-on services are off unless asked for. That is deliberate: a request that has always meant one thing should not quietly start costing more because we shipped something new.
Questions
- Which services run by default?
- The digital footprint runs on every lookup, because it is the original service and every request has always asked for it. Email, phone and IP intelligence are add-on modules, switched on per request through the checks object, so existing integrations are never billed for work they did not ask for.
- Can each service be called on its own?
- Yes. POST /v2/email, POST /v2/phone and POST /v2/ip each return one answer and skip the platform sweep, which is why a single IP check answers in a fraction of a second. The full API reference lives at api.digifootprint.dev and each service has its own documentation page.
- How are the services billed?
- Every service draws on one shared credit pool, so there is nothing separate to buy and no per-service subscription. A standalone check and a full lookup each cost one credit today.