WhoisFreaks Integration for Elastic

The WhoisFreaks integration collects data published by WhoisFreaks and indexes it into Elasticsearch:

• The daily gTLD and ccTLD newly registered domain ("domainer") feeds, with and without WHOIS records. These documents are enrichment data (event.kind: enrichment) under whoisfreaks.*: a newly registered domain is a risk signal, not an indicator of compromise, so these documents are not typed as threat indicators.
• The daily malware, phishing, and spam domain threat feeds. These documents are threat indicators (event.category: threat, event.type: indicator) with the domain in threat.indicator.url.domain and threat.indicator.name, and they are expired with an Elastic latest transform.

This integration requires a WhoisFreaks account and an API key from the WhoisFreaks billing dashboard, with:

• an active Domainer Subscription for the nrd_with_whois and nrd_without_whois data streams, and
• an active Threat Feed subscription for the threat_feed_malware, threat_feed_phishing, and threat_feed_spam data streams.

The integration contains five Elastic Agent CEL inputs. Every WhoisFreaks stream request requires a date query parameter (yyyy-MM-dd), so all five inputs work the same way:

1. On each poll, call the public WhoisFreaks status endpoint (/v3.4/status, no API key needed) and read that feed's last_update and available_from dates: newly.gtld and newly.cctld for the two newly registered domain streams, and threat_feed.malware, threat_feed.phishing, or threat_feed.spam for the threat feeds.
2. Pick the file date: the feed's last_update by default, or the configured File Date if one is set (see File Date). Every stream request carries this date parameter; only the status endpoint is called without one.
3. Compare it with the last file date already ingested for that feed, which is kept in the input cursor. If it is not newer, the poll ends after the status call, so the default 1h Interval never re-pages a daily file.
4. Otherwise, page through the stream endpoint with date, limit, and a growing offset until a page comes back short, then record the date as ingested.

Every column of every stream response is kept. CSV rows are mapped by the column names in the response's header row (the header of the first page is reused for later pages that do not repeat it), so a reordered or newly added column is indexed rather than dropped. Only empty cells are left out.

Every document carries the file date it came from in whoisfreaks.file_date. All inputs emit one document per row or domain.

File Date is optional on every data stream. Leave it empty (recommended) to always fetch the latest file reported by the status endpoint. When it is set, the input:

• Checks that the value is a real calendar date in yyyy-MM-dd format.
• Checks against the status endpoint that it falls within the feed's available_from..last_update range, inclusive (for the newly registered domain streams, separately for gTLD and ccTLD).
• Fetches a valid date once, and then continues with the latest file. Later polls follow the latest file even while the setting stays filled in. Changing the value fetches the new date once.
• If either check fails, indexes one error document that names the configured date and the allowed range, makes no stream request for that date, and continues with the latest file. If the date is valid for only one of gTLD/ccTLD, it is fetched for that feed.
• Tracks the pinned file separately from the latest ingested file, so fetching a historical file never causes the latest file to be fetched again.

Every status and stream request is checked. Failures are indexed as a single error document with error.code and an error.message that contains the method, the URL (the API key is always removed), the HTTP status, and the WhoisFreaks error and message text when the response is JSON.

• Server, timeout, rate-limit, and network errors (5xx, 408, 429, transport failures): the cursor is kept, so the next poll retries the same page.
• Authentication errors (401, 403, and the HTTP 400 Api Access Exception that WhoisFreaks returns for a missing or invalid API key): reported with a hint to check the API key and the Domainer or Threat Feed subscription; the cursor is kept and the next poll retries, so no file is skipped.
• Other client errors (for example 400 or 404): the file date is recorded as done for that feed so the input does not retry it forever; the newly registered domain streams move on to the other TLD type's pending file.
• Status endpoint failures (non-2xx, malformed JSON, missing feed, or a Not Available value): reported as an error document and no stream request is made.

The nrd_with_whois data stream uses the Elastic Agent CEL input to:

1. Query the public WhoisFreaks status endpoint (/v3.4/status) and read newly.gtld.last_update and newly.cctld.last_update. These are the dates of the latest available gTLD and ccTLD WHOIS files.
2. Compare each date against the last file of that type already ingested, which is tracked in two independent cursors in the input's persistent state.
3. For each feed with a newer date, page through the corresponding stream endpoint (/gtld or /cctld) with whois=true, date, limit, and a growing offset as query parameters, and the API key sent as the apiKey query parameter. Each page is parsed as a CSV with a header.
4. Emit each CSV row, tagged with tld_type (gtld or cctld), as a JSON message and advance that feed's cursor to the ingested date once paging for that feed completes. If a page request fails with a server, authentication, or rate-limit error, the cursor is kept, so the next poll resumes that page instead of skipping the day's file. Other client errors (for example an invalid File Date) are reported as an error event, that feed's file for the date is marked as done, and the input moves on to the other feed's pending file.
5. Run the result through an ingest pipeline that preserves the raw record in event.original, parses it into whoisfreaks.*, sets @timestamp, parses the WHOIS dates, derives whoisfreaks.days_until_expiry and whoisfreaks.is_newly_registered, and fingerprints tld_type + domain_name + query_time into the document _id for idempotent re-polling.

Each daily file holds only that day's newly registered domains, so no day is skipped after a gap (for example an agent outage or an error that lasts more than a day). When the last ingested date is older than the status last_update, the input fetches the following days one at a time, starting from the day after the last ingested date (or from available_from when that is later), until it reaches last_update. On the first run, the input starts from the current last_update. To load an older day, set File Date to it, wait for it to be ingested, and then clear the setting again.

The nrd_without_whois data stream follows the same daily status-driven pattern, but it requests the stream with whois=false. This endpoint returns the domain names as a plain newline-delimited list rather than a WHOIS CSV. The input:

1. Calls the public status API to discover the latest gTLD and ccTLD file dates.
2. Switches into the gtld or cctld paging mode only when that feed's date is newer than the last ingested value.
3. Splits the response body on \n, drops blank lines, and emits one event per non-empty domain entry with whoisfreaks.domain_name, the file date as whoisfreaks.query_time, and the matching whoisfreaks.tld_type tag.
4. Keeps the same cursor-based idempotency model as the WHOIS feed so it does not re-ingest identical daily snapshots.

Like the WHOIS feed, it uses a 1h default Interval, catches up missed days the same way, and polls without a new file only call the public status endpoint. Because this feed has no per-domain timestamp, whoisfreaks.query_time (and @timestamp) is the file date at 00:00:00 UTC.

The three threat feeds are daily snapshot endpoints under the WhoisFreaks v3.4 threat-feed API. Each input:

1. Reads threat_feed.<type>.last_update from the status endpoint (or uses the validated File Date) and, when that date is new, requests the feed endpoint for the relevant category (malware, phishing, or spam) with date, paging with limit and a growing offset until a page comes back short.
2. Emit each CSV row as the raw message, which the ingest pipeline preserves in event.original and parses by column name using the feed's header row. domain, first_seen, and last_seen populate the ECS indicator fields, and every other column (including any new one) is kept under whoisfreaks.threat_feed.<column>.
3. Emit one event per row with ECS threat fields (for example, threat.indicator.type and the feed-specific metadata).
4. Index upstream non-200 responses as error documents with error.code and error.message set rather than as threat indicators.

Each row is fingerprinted on threat.indicator.url.domain + threat.indicator.last_seen

• whoisfreaks.file_date into the document _id, so re-fetching the same file never duplicates documents. The latest transform keeps one document per domain: the copy from the newest daily file (by whoisfreaks.file_date). Rows of a file fetched once through File Date are flagged with whoisfreaks.pinned_file: true: they are kept in the source data stream as history but are excluded from the latest (active) indicator index, so a historical file never replaces or expires the indicators of the newest file. Indicators are expired as described in Expiration of Indicators of Compromise (IOCs).

Each threat feed file is a full daily snapshot. The Replace indicators from the previous file setting (enabled by default) controls what happens to indicators that a newer file no longer lists:

• Enabled: an indicator stays active until the next daily file is due (its file date plus 2 days, at 00:00 UTC), or until IOC Expiration Duration passes after last_seen, whichever comes first. Indicators repeated in the newest file get a later expiration from that file and stay active. Indicators missing from it are removed from the latest (active) indicator index automatically once the previous file's expiration passes, a few hours after the newest file is ingested. If no newer file is ingested (for example, during a long agent outage), the indicators from the last file also expire at that time.
• Disabled: indicators stay active until IOC Expiration Duration passes after last_seen, even if a newer file no longer lists them.

Elastic Agent cannot delete documents directly, so removal goes through the latest transform's retention policy. The raw documents in the source data stream are removed by its ILM policy. If IOC Expiration Duration cannot be parsed, the default of 90d is used and the documents are tagged invalid_ioc_expiration_duration.

The WhoisFreaks integration collects log messages of the following types:

• Domain WHOIS records for newly registered gTLDs and ccTLDs (with and without WHOIS enrichment).
• Malware, spam, and phishing domain threat indicators from the WhoisFreaks threat feeds.

• Domain portfolio management (expiration tracking).
• Threat intelligence / brand protection (newly registered domain monitoring, registrar/name-server pivoting).
• Registrar and TLD analytics.

• Elastic Agent.
• A WhoisFreaks account and API key with a Domainer Subscription (newly registered domain streams) and a Threat Feed subscription (threat feed streams).
• This integration installs Elastic latest transforms for the threat feeds. For more details, check the Transform setup and requirements.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

1. Sign in to the WhoisFreaks billing dashboard and confirm an active Domainer Subscription (for the newly registered domain streams) and Threat Feed subscription (for the threat feed streams).
2. Copy your API key from the dashboard.

• WhoisFreaks Newly Registered Domains API docs
• WhoisFreaks documentation home

1. Add the WhoisFreaks integration to an Agent policy.
2. Paste your API key in the integration-level API Key setting.
3. For each data stream, confirm the base URL (for the threat feeds this setting is under Advanced options). The defaults are already filled in:
   • nrd_with_whois and nrd_without_whois: the base domainer stream endpoint https://files.whoisfreaks.com/v3.3/stream/domainer, without the gtld/cctld suffix or query string.
   • threat_feed_malware, threat_feed_phishing, threat_feed_spam: https://files.whoisfreaks.com/v3.4/stream/threat-feed/{malware,phishing,spam}.
4. Leave File Date empty to always fetch the latest published file, or set a yyyy-MM-dd value within the feed's available range to fetch one historical file (see File Date). Keep each stream's Interval at its default, and adjust IOC Expiration Duration (default 90d) to control how long threat indicators stay active after they were last seen. Leave Replace indicators from the previous file enabled to keep only the indicators of the newest daily file active (see Replacing indicators from the previous file).
5. Save the integration and confirm the Agent starts collecting data.

Open Discover and validate each stream independently:

• logs-ti_whoisfreaks.nrd_with_whois-* for WHOIS-rich gTLD/ccTLD records.
• logs-ti_whoisfreaks.nrd_without_whois-* for daily domain-only records.
• logs-ti_whoisfreaks.threat_feed_malware-*, logs-ti_whoisfreaks.threat_feed_phishing-*, and logs-ti_whoisfreaks.threat_feed_spam-* for the three threat indicators.

Each stream should show documents with a populated whoisfreaks.domain_name or threat indicator fields and a valid @timestamp.

Check that the threat feed transforms are healthy:

1. In Kibana, navigate to Management > Stack Management.
2. Under Data, select Transforms.
3. In the search bar, type whoisfreaks.
4. All transforms from the search results should indicate Healthy under the Health column.

• No data is being collected: confirm the API key and the Domainer or Threat Feed subscription are valid; check error.code and error.message on error documents for the upstream HTTP status.
• Please provide the date parameter or outside the available range errors: check File Date. It must be yyyy-MM-dd and within the range that the status endpoint reports for that feed; leave it empty to follow the latest file.
• An upstream API failure (non-200 response) on any of the five data streams is indexed as a single document with error.code and error.message populated and no event.category, event.type, or threat.* fields set, so it is not mistaken for a normal indicator or WHOIS record. Search for them with the KQL query data_stream.dataset: ti_whoisfreaks.* AND error.message: *.
• Records that fail to parse are indexed with event.kind: pipeline_error, the failure in error.message, and the raw record in event.original.
• Since this integration expires threat indicators using an Elastic latest transform, the threat indicators are present in both the source and the destination indices. While this may appear to be duplicate ingestion, it is an implementation detail necessary for properly expiring threat indicators. Anticipate storage requirements accordingly.
• Security note: the WhoisFreaks API requires the API key to be sent as an apiKey query parameter. The key is redacted wherever this integration logs its internal state, but if Elastic Agent's HTTP client logging is raised to debug level (for example while troubleshooting), the outgoing request URL, including the API key may appear in agent logs in cleartext. Avoid enabling debug-level logging for this integration unless necessary, and treat agent debug logs as sensitive while doing so.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

These inputs can be used with this integration:

To collect logs via API endpoint, configure the following parameters:

• API Endpoint URL
• API credentials (tokens, keys, or username/password)
• Request interval (how often to fetch data)

These APIs are used with this integration:

• WhoisFreaks gTLD/ccTLD Newly Registered Domains stream API
• WhoisFreaks threat feed stream API (/v3.4/stream/threat-feed/malware, /phishing, and /spam)

• WhoisFreaks documentation
• WhoisFreaks WHOIS database download

The nrd_with_whois data stream provides Newly Registered Domains with WHOIS records.

{
    "@timestamp": "2026-08-03T09:54:02.000Z",
    "agent": {
        "ephemeral_id": "7f5ca59c-9b5a-42fb-809b-3476d1916302",
        "id": "2d6420b8-7d66-45e9-b7df-501c657d5e23",
        "name": "elastic-agent-85239",
        "type": "filebeat",
        "version": "8.19.21"
    },
    "data_stream": {
        "dataset": "ti_whoisfreaks.nrd_with_whois",
        "namespace": "42181",
        "type": "logs"
    },
    "ecs": {
        "version": "9.5.0"
    },
    "elastic_agent": {
        "id": "2d6420b8-7d66-45e9-b7df-501c657d5e23",
        "snapshot": false,
        "version": "8.19.21"
    },
    "event": {
        "agent_id_status": "verified",
        "dataset": "ti_whoisfreaks.nrd_with_whois",
        "ingested": "2026-10-19T07:09:15Z",
        "kind": "enrichment"
    },
    "input": {
        "type": "cel"
    },
    "related": {
        "hosts": [
            "echo-pinned.example",
            "ns1.example.net"
        ]
    },
    "tags": [
        "forwarded",
        "whoisfreaks-nrd-with-whois"
    ],
    "whoisfreaks": {
        "create_date": "2026-08-02T00:00:00.000Z",
        "days_until_expiry": 363,
        "domain_name": "echo-pinned.example",
        "domain_registrar_id": "9999",
        "domain_registrar_name": "Example Registrar Inc",
        "domain_registrar_url": "http://www.registrar.example",
        "domain_registrar_whois": "whois.registrar.example",
        "domain_status_1": "addperiod",
        "expiry_date": "2027-08-02T00:00:00.000Z",
        "file_date": "2026-08-03",
        "is_newly_registered": false,
        "name_server_1": "ns1.example.net",
        "num": 1,
        "query_time": "2026-08-03 09:54:02",
        "tld_type": "gtld",
        "update_date": "2026-08-02T00:00:00.000Z"
    }
}
		

The nrd_without_whois data stream provides Newly Registered Domains without WHOIS records.

{
    "@timestamp": "2026-08-03T00:00:00.000Z",
    "agent": {
        "ephemeral_id": "0a916111-60a1-4749-8c05-3113b41154ef",
        "id": "2dc2dfd8-f6a5-4972-9a3e-fad39d7bedca",
        "name": "elastic-agent-51208",
        "type": "filebeat",
        "version": "8.19.21"
    },
    "data_stream": {
        "dataset": "ti_whoisfreaks.nrd_without_whois",
        "namespace": "95130",
        "type": "logs"
    },
    "ecs": {
        "version": "9.5.0"
    },
    "elastic_agent": {
        "id": "2dc2dfd8-f6a5-4972-9a3e-fad39d7bedca",
        "snapshot": false,
        "version": "8.19.21"
    },
    "event": {
        "agent_id_status": "verified",
        "dataset": "ti_whoisfreaks.nrd_without_whois",
        "ingested": "2026-10-19T07:14:46Z",
        "kind": "enrichment"
    },
    "input": {
        "type": "cel"
    },
    "related": {
        "hosts": [
            "echo-pinned.example"
        ]
    },
    "tags": [
        "forwarded",
        "whoisfreaks-nrd-without-whois"
    ],
    "whoisfreaks": {
        "domain_name": "echo-pinned.example",
        "file_date": "2026-08-03",
        "query_time": "2026-08-03 00:00:00",
        "tld_type": "gtld"
    }
}
		

The threat_feed_malware data stream provides WhoisFreaks malware domain indicators.

{
    "@timestamp": "2026-08-24T22:10:05.500Z",
    "agent": {
        "ephemeral_id": "5fe6614e-b24e-4ec7-8a96-a611b147e83c",
        "id": "587ac4bf-1a68-486e-9959-f17bd0a57d99",
        "name": "elastic-agent-24746",
        "type": "filebeat",
        "version": "8.19.21"
    },
    "data_stream": {
        "dataset": "ti_whoisfreaks.threat_feed_malware",
        "namespace": "33935",
        "type": "logs"
    },
    "ecs": {
        "version": "9.5.0"
    },
    "elastic_agent": {
        "id": "587ac4bf-1a68-486e-9959-f17bd0a57d99",
        "snapshot": false,
        "version": "8.19.21"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "threat"
        ],
        "dataset": "ti_whoisfreaks.threat_feed_malware",
        "ingested": "2026-10-19T07:35:53Z",
        "kind": "enrichment",
        "original": "malware-host-2.example,malware,0.85,2026-07-01 08:00:00+00,2026-08-24 22:10:05.5+00,3",
        "type": [
            "indicator"
        ]
    },
    "input": {
        "type": "cel"
    },
    "tags": [
        "preserve_original_event",
        "forwarded",
        "whoisfreaks-threat-feed-malware"
    ],
    "threat": {
        "indicator": {
            "confidence": "High",
            "first_seen": "2026-07-01T08:00:00.000Z",
            "last_seen": "2026-08-24T22:10:05.500Z",
            "name": "malware-host-2.example",
            "provider": "WhoisFreaks",
            "reference": "https://whoisfreaks.com/",
            "type": "domain-name",
            "url": {
                "domain": "malware-host-2.example"
            }
        }
    },
    "whoisfreaks": {
        "file_date": "2026-08-25",
        "threat_feed": {
            "confidence": 0.85,
            "deleted_at": "2026-08-27T00:00:00.000Z",
            "ioc_expiration_duration": "5d",
            "no_of_threat_matched_pivots": 3,
            "threat_type": "malware"
        }
    }
}
		

The threat_feed_spam data stream provides WhoisFreaks spam domain indicators.

{
    "@timestamp": "2026-08-24T22:10:05.500Z",
    "agent": {
        "ephemeral_id": "99169704-9475-40a2-b6c0-64025139d1c0",
        "id": "a037cc3c-9660-489a-a20d-7cf5ee5e4424",
        "name": "elastic-agent-37950",
        "type": "filebeat",
        "version": "8.19.21"
    },
    "data_stream": {
        "dataset": "ti_whoisfreaks.threat_feed_spam",
        "namespace": "77706",
        "type": "logs"
    },
    "ecs": {
        "version": "9.5.0"
    },
    "elastic_agent": {
        "id": "a037cc3c-9660-489a-a20d-7cf5ee5e4424",
        "snapshot": false,
        "version": "8.19.21"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "threat"
        ],
        "dataset": "ti_whoisfreaks.threat_feed_spam",
        "ingested": "2026-10-19T07:32:12Z",
        "kind": "enrichment",
        "original": "spam-sender-2.example,spam,0.85,2026-07-01 08:00:00+00,2026-08-24 22:10:05.5+00,3",
        "type": [
            "indicator"
        ]
    },
    "input": {
        "type": "cel"
    },
    "tags": [
        "preserve_original_event",
        "forwarded",
        "whoisfreaks-threat-feed-spam"
    ],
    "threat": {
        "indicator": {
            "confidence": "High",
            "first_seen": "2026-07-01T08:00:00.000Z",
            "last_seen": "2026-08-24T22:10:05.500Z",
            "name": "spam-sender-2.example",
            "provider": "WhoisFreaks",
            "reference": "https://whoisfreaks.com/",
            "type": "domain-name",
            "url": {
                "domain": "spam-sender-2.example"
            }
        }
    },
    "whoisfreaks": {
        "file_date": "2026-08-25",
        "threat_feed": {
            "confidence": 0.85,
            "deleted_at": "2026-08-27T00:00:00.000Z",
            "ioc_expiration_duration": "5d",
            "no_of_threat_matched_pivots": 3,
            "threat_type": "spam"
        }
    }
}
		

The threat_feed_phishing data stream provides WhoisFreaks phishing domain indicators.

{
    "@timestamp": "2026-08-24T22:10:05.500Z",
    "agent": {
        "ephemeral_id": "99dd826c-6bfb-466f-baef-fa0eaa975c2e",
        "id": "5ca6ba45-a3d1-4cac-904f-dc15ff0952ef",
        "name": "elastic-agent-89860",
        "type": "filebeat",
        "version": "8.19.21"
    },
    "data_stream": {
        "dataset": "ti_whoisfreaks.threat_feed_phishing",
        "namespace": "77540",
        "type": "logs"
    },
    "ecs": {
        "version": "9.5.0"
    },
    "elastic_agent": {
        "id": "5ca6ba45-a3d1-4cac-904f-dc15ff0952ef",
        "snapshot": false,
        "version": "8.19.21"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "threat"
        ],
        "dataset": "ti_whoisfreaks.threat_feed_phishing",
        "ingested": "2026-10-19T07:29:05Z",
        "kind": "enrichment",
        "original": "phish-login-2.example,phishing,0.85,2026-07-01 08:00:00+00,2026-08-24 22:10:05.5+00,3",
        "type": [
            "indicator"
        ]
    },
    "input": {
        "type": "cel"
    },
    "tags": [
        "preserve_original_event",
        "forwarded",
        "whoisfreaks-threat-feed-phishing"
    ],
    "threat": {
        "indicator": {
            "confidence": "High",
            "first_seen": "2026-07-01T08:00:00.000Z",
            "last_seen": "2026-08-24T22:10:05.500Z",
            "name": "phish-login-2.example",
            "provider": "WhoisFreaks",
            "reference": "https://whoisfreaks.com/",
            "type": "domain-name",
            "url": {
                "domain": "phish-login-2.example"
            }
        }
    },
    "whoisfreaks": {
        "file_date": "2026-08-25",
        "threat_feed": {
            "confidence": 0.85,
            "deleted_at": "2026-08-27T00:00:00.000Z",
            "ioc_expiration_duration": "5d",
            "no_of_threat_matched_pivots": 3,
            "threat_type": "phishing"
        }
    }
}
		

The threat_feed_malware, threat_feed_phishing, and threat_feed_spam data streams expire threat indicators after the duration configured in the IOC Expiration Duration setting (default 90d), counted from threat.indicator.last_seen, or earlier when Replace indicators from the previous file is enabled (see Replacing indicators from the previous file). An Elastic Transform is created for every source index to make sure only active threat indicators are available to the end users. Each transform creates a destination index named logs-ti_whoisfreaks_latest.dest_* which only contains active and unexpired threat indicators. Destination indices are aliased to logs-ti_whoisfreaks_latest.<data_stream_name>.

To facilitate IoC expiration, source data stream-backed indices .ds-logs-ti_whoisfreaks.<data_stream_name>-* are allowed to contain duplicates from each polling interval. ILM policy logs-ti_whoisfreaks.<data_stream_name>-default_policy is added to these source indices, so it doesn't lead to unbounded growth. This means that in these source indices data is deleted about 5 days after it was ingested.

• Description: Latest WhoisFreaks malware domain indicators.
• Source Index: logs-ti_whoisfreaks.threat_feed_malware-*
• Destination Index: logs-ti_whoisfreaks_latest.dest_threat_feed_malware-1

• Description: Latest WhoisFreaks phishing domain indicators.
• Source Index: logs-ti_whoisfreaks.threat_feed_phishing-*
• Destination Index: logs-ti_whoisfreaks_latest.dest_threat_feed_phishing-1

• Description: Latest WhoisFreaks spam domain indicators.
• Source Index: logs-ti_whoisfreaks.threat_feed_spam-*
• Destination Index: logs-ti_whoisfreaks_latest.dest_threat_feed_spam-1

The integration installs two dashboards. Open them from Analytics → Dashboard after install (filter by tag WhoisFreaks).

[Logs WhoisFreaks] Overview (opens on the last 7 days) covers the newly registered domain data streams:

• nrd_with_whois: total records, unique domains, and unique registrars; records over time; top registrars and name servers; domains table
• nrd_without_whois: domain count and domains over time

[Logs WhoisFreaks] Threat Feeds (opens on the last 90 days) covers the active (latest) indicators from the threat_feed_malware, threat_feed_phishing, and threat_feed_spam transforms:

• Active indicators, unique domains, and average confidence
• Active indicators by last seen, split by feed
• Indicators by feed, confidence, and threat type
• Most recently seen indicators table

The threat feed indicators set threat.feed.dashboard_id to this dashboard, so the Security Intelligence page links each WhoisFreaks feed to it.

Note on whoisfreaks.days_until_expiry: this value is computed once at ingest time as the difference between the record's query_time and its expiry_date. It is not recomputed as time passes. If you need an up-to-date value, compute days-to-expiry from whoisfreaks.expiry_date against now (for example, a runtime field) rather than relying on the stored value.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×