How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

DomainTools Iris Investigate API

The Iris Investigate API is ideally suited for investigate and orchestrate use cases at human scale. Identify threats, map adversary infrastructure, and streamline investigations.

DomainTools Iris Investigate API is one of 12 APIs that DomainTools publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Iris Investigate. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 2 operations across 1 path, and defines 48 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.domaintools.com.

2 operations 1 paths 48 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.domaintools.com
Authentication
API Key, HTTP Basic, API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 3

DomainTools Iris Investigate API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (header_auth). It accepts HTTP basic authentication (open_key_auth). An API key is passed in the query as signature (hmac_auth). By default, every request must be authenticated.

  • header_auth — A secure authentication method where the API key is provided in the X-Api-Key HTTP request header.
  • open_key_auth — A simple authentication scheme using your apiusername as the username and your apikey as the password. We strongly recommend using HMAC or Header authenticatio…
  • hmac_auth — A secure scheme using a Hashed Message Authentication Code (HMAC). This method requires three query parameters to be sent with the request: 1. apiusername: You…

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Iris Investigate 2

The Iris Investigate API is ideally suited for investigate and orchestrate use cases at human scale. Identify threats, map adversary infrastructure, and streamline investigations.

GET
/v1/iris-investigate/
Returns data from a GET request. Parameters are identified in descriptions as either base or filter. Search with base parameters and filter down base results with filter parameters.
getIrisInvestigate 71 params → 200206400401403404500503
POST
/v1/iris-investigate/
Returns data from a POST request.
postIrisInvestigate body → 200206400401403404500503

Schemas 48

The contract defines 48 schemas that model the data the API accepts and returns. The most detailed are InvestigateRequestParameters (71 properties), DomainProfileTemplate (47 properties), InvestigateResult (33 properties), BaseSslInfo (11 properties). Each schema is shown below with its type and property counts.

IdentifierString
string
A short identifier, code, or handle.
OrgNameString
string
A human-readable organization name as used in WHOIS or RDAP records, such as a registrar, registrant, or sponsoring organization. Supports Unicode letters and…
PivotedTracker
object
A tracker identifier and its associated pivot count.
2 properties
RiskScoreValue
integer
A domain risk score value ranging from 0 (lowest risk) to 100 (highest risk).
BasicString
string
A non-empty string with a standard length limit.
DomainRisk
object
Domain risk assessment including overall score and contributing components.
2 properties
ThreatProfileMalware
object
Indicates risk based on a machine-learning model that classifies domains as malware-related.
3 properties 2 required
SearchHashToken
string
Opaque token representing a saved search from the Iris Investigate UI. Exported via “Search → Export” in the Iris UI. Example: aGVsbG93b3yY2hfaGFzaF9jb2RlJsZF9…
ApexDomainList
string
A comma-separated list of one or more apex domains to investigate.
ThreatProfilePhishing
object
Indicates risk based on a machine-learning model that classifies domains as phishing-related.
3 properties 2 required
DateOperatorsFilter
string
A date in YYYY-MM-DD format, optionally prefixed with an operator (, =, <, <=) for comparison. Example: <=2025-01-01
PositionToken
string
An opaque string token used for cursor-based pagination. Returned in the position field of a paginated response when hasmoreresults is true, and used as a quer…
BaseSslInfo
object
A template for SSL certificate information blocks.
11 properties
Proximity
object
Indicates risk based on proximity to known threats or suspicious infrastructure.
3 properties 2 required
Fqdn
string
A Fully Qualified Domain Name (FQDN), including subdomains (e.g., www.example.com). Must be a valid DNS hostname per RFC 1123, excluding trailing dot.
ResponseFormat
string
The desired response format.
SslSubjectDnString
string
A distinguished name (DN) string representing the Subject field of an SSL certificate. Typically includes components like CN, O, C, ST, and L in a comma-separa…
TopLevelDomain
string
A top-level or public suffix domain, such as com, org, or co.uk. Must not include a leading dot.
TimeWindowSeconds
integer
A positive integer representing a time window, in seconds. Used to filter results based on how recently an event occurred.
CommaSeparatedTags
string
A comma-separated list of tag names. Tags are matched exactly and compared case-insensitively unless otherwise specified.
HtmlResponse
string
HTML-formatted response body. JSON is the primary documented format; HTML response schemas are not individually documented.
BooleanOptInFlag
boolean
An optional boolean flag that enables a specific feature or response extension when set to true. If false or omitted, the feature is ignored.
Hostname
string
A valid, fully-qualified domain name (FQDN).
GenericString
string
A generic and unconstrained string value.
DomainProfileTemplate
object
A comprehensive template defining the complete structure of a domain profile. Specific data types are defined in inheriting schemas.
47 properties
DomainRiskComponent
A polymorphic schema representing one of several types of risk components.
XmlResponse
string
XML-formatted response body. JSON is the primary documented format; XML response schemas are not individually documented.
DateFilter
string
A calendar date in the format YYYY-MM-DD, per RFC 3339 (full-date). Does not include a time or timezone.
IPv4Address
string
A standard IPv4 address.
InvestigateResult
object
33 properties
EmailAddress
string
A valid email address, as defined by RFC 5322 and commonly used in WHOIS, SSL certificates, RDAP records, or domain registration contacts.
ApexDomain
string
A base (apex) domain like example.com, excluding subdomains.
ZeroListedScore
object
Indicates the domain is on a known-good 'zero list' and is not considered a threat.
2 properties 2 required
MaxDaysSince
integer
A positive integer representing the maximum number of days.
TimestampFilter
Defines a point in time for filtering results. Accepts one of: - relative time, in negative seconds - absolute time, in an ISO 8601 timestamp
Sha1HexString
string
A 40-character hexadecimal SHA-1 hash string, typically used to identify SSL certificates or digital signatures.
ThreatProfileSpam
object
Indicates risk based on a machine-learning model that classifies domains as spam-related.
3 properties 2 required
WhoisContact
object
Contact details from a WHOIS record.
10 properties
InvestigateRequestParameters
object
71 properties
PivotedValue
object
2 properties
ThreatProfile
object
Indicates risk based on machine-learning models.
3 properties 2 required
ParsedWhois
object
Parsed data from the domain's WHOIS record. Present only when the request includes parsedwhois=true.
10 properties
BaseContact
object
A template for contact information blocks.
10 properties
RdapContact
object
Contact details from an RDAP record.
10 properties
WebsiteTitleString
string
The exact value of the tag from a website's HTML.
ErrorResponse
object
2 properties
PivotedContact
object
10 properties
ParsedDomainRdap
object
Parsed data from the domain's RDAP record. Present only when the request includes parseddomainrdap=true.
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

domaintools-iris-investigate-api-openapi.yml Raw ↑

Other APIs DomainTools publishes across the network.

DomainTools Flex search API
DomainTools Information API
DomainTools Iris Detect API
DomainTools Iris Enrich API
DomainTools Lookups API
DomainTools Monitors API
DomainTools Ping API
DomainTools Rate Limit API
DomainTools rdata Lookups API
DomainTools rrset Lookups API
DomainTools Siebatchd API
Where this information came from

This is an independent, third-party profile of DomainTools Iris Investigate API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.