Netify - Legacy Application Domains Dataset

Legacy Application Domains

If you signed up to Netify Data Feeds after October 2024, please follow the current Application Domains guide.

For those of you still using the legacy Application Domains dataset, you can find technical details below. We recommend migrating to the new dataset -- it is one simple download -- no pagination required. Please contact us to update your API access.

Getting Started

You can find general Netify API information on Authentication, Response Codes, and other topics in the menu. You can also find JSON format information on our standard data objects: IP object, application object, etc.

Postman Documentation

API Quick Reference

Route	https://feeds.netify.ai/api/v2/intelligence/application_domains/{application_tag}
Authentication	x-api-key
Pagination	100

Data Payload

The Netify Legacy Application Domains Dataset is an API that provides the following application details:

Application Information and logos
Domains

We break down both of these items in the following sections.

Application Property

Every item in the payload list starts with our standard application property. This provides the application name, description, logo, and other details.

Domain List

The domain list contains all the domain definitions used to detect an application. For example, the following is a sample of domains used to match the Twitter application:

t.co
twimg.com
twitter.com
twimg.com.akahost.net
twitter.map.fastly.net
etc.

These domains are used to identify application network traffic flows via Netify DPI processing. The hostnames coming from TLS SNI, TLS certificate common names, HTTP headers, DNS requests, DNS hinting, and any hostname that pops out of deep packet inspection are compared to the domain lists.

Please note: for companies with large portfolios of applications, the subdomains can be important differentiators. For example, the googleapis.com domain is part of the Google domain list, but the youtubei.googleapis.com domain is part of Google-owned YouTube domain list.

If a domain belongs to a platform, the metadata is attached to the payload.

JSON Overview

"data": {
    { Application Property },
    [ Domain List ]
}

Domain List JSON Overview

"domain_list": [
    {
        "id": 2737771,
        "label": "twimg.com.akahost.net",
        "category": {
            "id": 24,
            "tag": "social-media",
            "label": "Social Media"
        },
        { Platform Object }
    }

Domain List JSON Example

"domain_list": [
    {
        "id": 2737771,
        "label": "twimg.com.akahost.net",
        "category": {
            "id": 24,
            "tag": "social-media",
            "label": "Social Media"
        },
        "platform": {
            "id": 1002,
            "tag": "akamai",
            "label": "Akamai",
            "category": {
                "id": 2,
                "tag": "cdn",
                "label": "CDN"
            },
        }
    },