Lookup API

Seven focused products before a recursive scan.

Every lookup accepts one bounded input and uses one versioned product recipe. The page shows route readiness, configuration and exclusions from the generated product catalogue.

Exact public contract

Choose the bounded question you need answered.

Four recipes are free-compatible and synchronous. Three authenticated recipes create retained jobs with lane progress, evidence and explicit partial or unavailable states.

AvailableFree

MAC / OUI lookup

Accepts mac address. Returns its bounded projection synchronously.

Public route
POST /v2/lookups/mac
Required lanes
vendor assignment
Optional lanes
None
Required configuration
None

Returned fieldsnormalizedMac, assignment, traits, datasetVersion, datasetFingerprint, evidenceSummary, limitations

Claims excludeddevice owner, person identity, location

AvailableFree

Phone format and region lookup

Accepts phone number. Returns its bounded projection synchronously.

Public route
POST /v2/lookups/phone
Required lanes
numbering metadata
Optional lanes
None
Required configuration
None

Returned fieldsexactInput, normalizedE164, possible, valid, countryCallingCode, regionCode, numberType, formats, dataVersion, evidenceSummary, limitations

Claims excludedsubscriber owner, person identity, reachability

AvailableFree

IP context lookup

Accepts ip address. Returns its bounded projection synchronously.

Public route
POST /v2/lookups/ip
Required lanes
address classification
Optional lanes
routing context, allocation context, reverse dns
Required configuration
None

Returned fieldsexactInput, normalizedIp, requiredFacts, optionalContext, unavailableLanes, sourceFingerprints, limitations

Claims excludedlegal owner, precise location

Partially configuredFree

DNS lookup

Accepts domain name, hostname. Returns its bounded projection synchronously.

Public route
POST /v2/lookups/dns
Required lanes
dns answers
Optional lanes
resolver consensus, dnssec dane
Required configuration
TIGESS_DNS_RESOLVERS

Returned fieldsqueryName, answers, outcomes, dnsStatus, dnssecSummary, sourceMetadata, limitations

Claims excludedservice absence, ownership, identity

AvailableAuthenticated · credits

Domain core lookup

Accepts domain name, hostname. Creates one retained asynchronous lookup job.

Public route
POST /v2/lookups/domain
Required lanes
dns core, registration core
Optional lanes
rdap context, certificate context, first party web facts
Required configuration
None

Returned fieldsdomain, registration, dns, certificates, web, relationships, lanes, evidenceSummary, limitations

Claims excludedregistrant legal ownership, allocation legal ownership, offsite active fanout

AvailableAuthenticated · credits

Mail security lookup

Accepts domain name. Creates one retained asynchronous lookup job.

Public route
POST /v2/lookups/mail
Required lanes
server topology, authentication records
Optional lanes
dkim selectors, transport policy
Required configuration
None

Returned fieldsdomain, topology, authentication, transport, checks, findings, lanes, selectorCoverage, evidenceSummary, limitations

Claims excludedall clear, unchecked policy absence, mailbox reachability, provider ownership

AvailableAuthenticated · credits

Web and TLS posture lookup

Accepts domain name, hostname, url. Creates one retained asynchronous lookup job.

Public route
POST /v2/lookups/web
Required lanes
http headers, page metadata, tls certificate
Optional lanes
security txt, technology fingerprints
Required configuration
None

Returned fieldssubmittedUrl, endpoint, redirects, tls, headers, securityTxt, technologies, findings, lanes, networkTelemetry, evidenceSummary, limitations

Claims excludedpenetration test, offsite active expansion, confirmed version from candidate, vulnerability from fingerprint

Need retained lookup results?

Use the API product before increasing breadth.

Domain Core, Mail Security and Web/TLS Posture are fixed, non-recursive recipes. They keep required and optional lanes visible.

Need evidence-routed expansion?

Compare the four scan profiles. Recursive fan-out schedules only compatible work from retained results and stops at profile, request, safety and credit bounds.

Compare scan profiles