What ArkOwl can reveal about an email address

Two loan applications arrive in your queue a few minutes apart. You open them expecting the usual differences in income, amount, channel, or eligibility details. Instead, the forms line up almost perfectly. Same product, same requested amount, same channel, and both clear the rules you already trust. Only the email addresses differ. One looks as though it has been in use for years. The other appears to have been created that morning, just in time for the application. Your existing checks have treated the addresses as interchangeable. Should they be carrying the same weight in the decision?

What one lookup returns

You make one HTTPS GET request per email address. Its response can include how often and since when the address has been seen, account registration information for services such as Google, and details about the domain. It can also report known aliases, data breaches and reported bad activity, along with an email age or creation date.

Rob Daline of ArkOwl describes the fraud concern plainly: “the email address is the easiest piece of information to create and fake” for someone seeking to defraud or steal. That makes the history behind an address useful context alongside your other checks. Email checks sit beside other checks in rules against junk logins and bot attacks.

History is evidence someone is real

An address is easy to create, and a history of sightings and an account at an established service are much harder to fabricate, as our lookups show.

A new address can pass blacklists because it has not yet been reported. History can offer a signal that a blacklist cannot. Years of sightings and an account at a service such as Google do not prove that an applicant is genuine, but they can help you assess the possibility of a synthetic identity.

Null means unknown

ArkOwl returns null when it cannot make a conclusive decision about a piece of data. Its account-check statuses also distinguish a registered account from an unregistered one, an inconclusive check and a check that was not performed. Treat unknown as its own result, rather than reading it as false.

This distinction matters in a decision table because a missing numeric value reads as zero unless a row catches null explicitly. You can reward evidence of history and give null its own branch.

The domain tells you what kind of mailbox it is

ArkOwl can identify a disposable email provider on the domain and return a description of the service. In one lookup, its description called the service “one of the original disposable email services used primarily by developers and QA testers” and noted that public inboxes can be viewed by anyone who knows the address.

The domain can also carry a free-email-provider flag.

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

Start free See pricing

Count your own lookups

A lookup can add to the history ArkOwl reports. A fresh address on our domain had no sightings on its first lookup. When it was looked up again minutes later, ArkOwl reported one sighting and a first-seen time matching the earlier lookup.

Look up an address once per application and keep that response for the decision. Then a retry reads that first response, so your own lookups do not add to the history the decision reads.

Turning ArkOwl into a score

ArkOwl’s suggested scoring model has 35 conditions that add or subtract points. For example, it subtracts four points when an email is on its bad-activity blacklist. It adds one point for a Microsoft account. A domain first seen within the model’s stated 90-day window subtracts two points. These weights are ArkOwl’s suggestion, not advice.

Eleven conditions in the model compare dates. ArkOwl returns its dates as UNIX timestamps, so put a date comparison in a rule with a time condition. Another option is to use a function to turn the timestamp into an age in days, then band that number in a scorecard.

Fraud decision flow

1. Look up the address once when the application arrives, alongside your other sources.
2. Reward evidence of history and registered accounts in the decision.
3. Give null its own branch, separate from a result that is affirmatively false.
4. Read the disposable-provider and free-email flags on the domain.
5. Put date comparisons in rules, or convert a timestamp to an age in days before assigning a score band.
6. Choose how your rules should handle a failed call. ArkOwl’s values come back absent with an error flag, so the decision logic determines what follows.

Where it fits

Account opening

At account opening, an address’s history and account information can add context to the details supplied on the application.

Loan applications

For a loan application, a long history and accounts at established services can help you assess whether the identity may be synthetic.

Checkout

At checkout, the domain’s disposable-provider or free-email flag can contribute to your assessment of an address. Consider those details with the history ArkOwl reports.

Frequently asked questions

Does an address with no history mean fraud?

No. A lack of reported history does not establish fraud. ArkOwl returns null when it cannot make a conclusive decision, so keep that result distinct from an affirmative false value.

Should I use API v1 or v2?

ArkOwl’s v1 returns account statuses as text. V2 expresses account checks as true or false, with null for an inconclusive result. Choose the representation that fits the way your rules handle those results.

What does ArkOwl cost?

ArkOwl does not publish a price. It offers a monthly subscription or prepaid queries, and a free trial.

Is ArkOwl an alternative to SEON?

Yes. ArkOwl is useful as an alternative to SEON for knowing who stands behind an email address. It gives your team email and phone evidence on its own, including history, registered accounts, domain flags, and null where it cannot reach a conclusive answer, plus what can be inferred from the raw data, so your own rules make the decision.

Is ArkOwl an alternative to Trustfull?

Yes. ArkOwl is useful as an alternative to Trustfull for knowing who stands behind an email address. It hands over raw email and phone data for your rules to weigh, including history, registered accounts, domain flags, and null where it cannot reach a conclusive answer, with the optional ArkVision score for a team that wants one.

What do the API errors mean?

A 402 means the account is out of query credits, and a 401 that no valid API key was sent.

To connect ArkOwl, store its API key once as an HTTP Basic credential. Use the key as the username and leave the password empty, written as key:. The data source refers to that saved credential. The assistant can configure the data source from ArkOwl’s documentation, and you review and approve the configuration.

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

Start free See pricing