Iris Rate Limits¶

This document explains rate limits and quota consumption for Iris Investigate, Iris Enrich, and Iris Detect in both the API and UI.

Check your rate limits¶

Use the following methods to determine the current rate limit associated with Iris Investigate, Iris Enrich, and Iris Detect API endpoints:

/account Endpoint
Querying the Account Information endpoint provides details on query limits, usage, and expiration dates for all licensed Iris endpoints.
For more information, refer to the Account Information endpoint documentation.
API Admin Dashboard
The API Admin can access their API dashboard to view query limits, usage, and expiration dates for all licensed endpoints.
To access the API dashboard, visit the DomainTools research page, select the account dropdown menu, and click on API Admin.

Free test queries¶

Multiple endpoints, including Iris Detect and Investigate, offer free test queries that don't count against your quota. Use these domains for testing and development:

domaintools.com
dnsdb.info
example.com

Endpoints with free test queries¶

The following endpoints support free test queries with the domains listed above:

Domain Profile, Domain Reputation, Hosting History, Iris Enrich and Investigate, Reverse IP, WHOIS history, WHOIS Lookups

Using these test domains allows you to verify API integration and test functionality without consuming your quota.

Iris Investigate rate limits and quota consumption¶

The system measures quotas at the group level and resets them each month.

Duplicate query policies¶

Iris Investigate treats identical queries differently depending on whether you use the UI or API:

User Interface¶

Identical queries within 30 days don't count against your quota. This includes:

All searches (omnisearch and advanced search)
Search hash queries
Search hash reloading
Search node revisits

A query is considered identical if it has the same filters, sorting, and pagination parameters.

API¶

Regular queries: Identical queries within 1 hour don't count against quota. A query is considered identical if it has the same filters, sorting, and pagination parameters as a previous query made within the last hour.

Search hash queries: Identical search hash queries within 10 minutes don't count against quota. A search hash query uses the search_hash parameter to retrieve previously saved search results.

Activities that consume quota¶

Pivot Engine Queries in the Iris Investigate UI¶

The following activities consume your quota:

Executing an omnisearch (from landing or search pages) that returns results
Executing an advanced search that returns results
Sending a result to the Pivot Engine (including narrow, expand, new, and exclude functions)
Revisiting a search node more than 30 days since it was created
Loading new pages in the Pivot Engine
Sorting Pivot Engine results

For information on duplicate queries that don't consume quota, see Duplicate query policies.

Passive DNS (pDNS) Queries in the Iris Investigate UI¶

The following activities consume your quota:

Executing a search query that returns results (from either the search field or popovers throughout the UI)
Executing/triggering the load more (infinite scroll) function in search results
Revisiting a search node more than 30 days since it was created

For information on duplicate queries that don't consume quota, see Duplicate query policies.

Queries in the Iris Investigate API¶

The following activities consume your quota:

Executing a query
Loading additional pages of results

For information on duplicate queries that don't consume quota, see Duplicate query policies.

Iris Enrich rate limits¶

Iris Enrich uses an independent service level with its own rate limits, separate from Iris Investigate. This independence allows Iris Enrich to be used at much greater scale and throughput than Iris Investigate.

Key differences:

Independent quota: Enrich queries don't count toward your Iris Investigate quota
Separate service level: Rate limits are defined independently for Enrich
Higher throughput: Optimized for high-volume domain enrichment use cases
No pivot parameters: Unlike Investigate, Enrich is optimized for straightforward domain enrichment rather than pivoting

Your Enrich service level, query caps, and rate limits are configured independently on your enterprise account. For complete details on using Iris Enrich, consult the Iris Enrich API documentation.

Iris Detect rate limits¶

Iris Detect has specific endpoint rate limits designed for monitoring and triage workflows.

Domain endpoints rate limits¶

The domains endpoints (/domains/new and /domains/watched) have a rate limit of 1 query per hour for each endpoint.

Pagination: Requests using the offset parameter to retrieve additional pages of results aren't restricted by the hourly limit. If your hourly query returns more domains than the response limit, you can retrieve the complete result set using pagination without waiting.

Development and testing¶

During integration and testing, use the preview parameter to bypass rate limits:

Including preview=1 in requests limits responses to 2 domains
Allows up to 30 requests per minute
Enables rapid iteration during development

Other endpoints¶

Monitor management endpoints and domain triage actions (watchlist, ignore, escalate) have standard API rate limits. For complete details on Iris Detect API endpoints and usage, consult the Iris Detect API documentation.