The Discovery & Attribution API provides a RESTful interface to over a decade’s worth of carefully managed and maintained attribution data.

General Information

Dyn’s Discovery & Attribution API enables operations teams, analysts and security professionals to quickly gather accurate intelligence to identify the ownership, provenance and routing connectivity profile of any network.


Components of Discovery & Attribution API

The Discovery & Attribution API enables you to perform 4 types of asset search:

IP: Identifies the label associated with the designated IP address, together with routing information, including the originating Autonomous System Number (ASN) and covering prefix.

Prefix: Identifies the assignment, label, routing information for the designated IP prefix.

ASN: Identifies the peers, providers and customers for the specified ASN.

General Search: Enables discovery and identification of IP prefixes and ASNs given an input string.

Accessing the API

To invoke the Attribution API, each request requires an API-DynID and a API-Key combination for authentication.

These fields are separated by a colon for basic authentication, e.g. API-DynID:API-Key.

Typically, the API-Key will contain many special characters and you should wrap the API-DynID:API-Key in single quotes if using curl on the command line:

e.g. curl -u '{API-DynID}:{API-Key}' {URL}.

You can generate the API DynID and API Key using the instructions found here: DynID – II Attribution API Keys (API Key Creation).

Data Sources

The Discovery & Attribution data set combines information from a wealth of sources, including:

200 million daily IPv4 and IPv6 BGP routing announcements collected from our 600+ global collectors.

Over 5 billion daily latency measurements used for geolocation validation and improvement.

The system contains 36 million current asset records, plus 350 million more historical records, pertaining to 17 million unique prefixes and nearly 60 thousand ASNs

Dyn’s REST API allows for simple HTTPS interaction with a variety of data encoding formats.

The API strives to use appropriate HTTP verbs for each action. The current methods are limited to retrieving resources.


GET Used for retrieving resources.

The Discovery and Attribution API supports the JSON (application/json) content type to interact with the REST interface.


Each invocation of the API produces a response in the JSON format.

200 OK – The action was successful.
201 Resource was successfully created.
204 Resource was successfully deleted.
400 Error in request.
404 Resource not found.