datapulse_dns_regclusters
datapulse:dnsRead-onlyFind registrars that registered many domains on one UTC day, from the corpus’s RDAP registration records: bulk campaigns, parking inventory, …
Description
Find registrars that registered many domains on one UTC day, from the corpus’s RDAP registration records: bulk campaigns, parking inventory, volume spikes.
Summary (default): clusters, one row per registrar with domain_count and up to 10 SAMPLE domains, largest first. There are no pages: when limit rows come back, complete: false says more clusters may exist (raise limit or min_cluster_size).
Detail (registrar_id set): domains registered at that registrar that day, alphabetically, with total; returned, offset, truncated and next_offset page them, and a page with truncated: true is a SUBSET whose note names date= and offset= for the next call.
Every row carries registrar_id and registrar_id_scheme: “iana” (an IANA ID, with registrar_name, resolvable with datapulse_dns_registrar), “registry” (the registry’s own number, which no IANA lookup resolves) or “unresolved”. registrar_id is what to pass back as registrar_id in any case.
Without date, the latest UTC day of the last 7 with a normal volume is answered, the same day for every page, and the note says which. A day’s registrations keep arriving for about three weeks, so recent counts are floors. Large registrars register tens of thousands a day; min_cluster_size=100 or more filters them.
Reference: datapulse_help(topic="infrastructure")
Parameters
| Parameter | Type | Description |
|---|---|---|
date | string | Date to search for registrar clusters (YYYY-MM-DD format), a UTC day: registrations from 00:00 to 24:00 UTC. When omitted, the most recent UTC day (within the last 7) with a normal volume of registrations is used, the same day for every page, and the response says which. Max length: 10Pattern: ^\d{4}-\d{2}-\d{2}$ |
limit | integer | Summary mode: registrar clusters, default 25, max 80 (up to about 700 bytes each). Detail mode: domains per page, default 200, max 500 (about 100 bytes each). Larger values are capped; 0 or less is the default. |
min_cluster_size | integer | Summary mode only: minimum number of domains a registrar must have registered on that date to be included, 2 or more, default 8. Higher values (50, 100, 500) keep only large bulk campaigns. Refused with registrar_id. |
offset | integer | Detail mode only (registrar_id set): domains to skip (alphabetical order), from a previous response’s next_offset, default 0; a negative offset is refused. A nonzero offset is refused in summary mode, which has no pages. |
registrar_id | integer | Registrar identifier to drill into, exactly as a summary row’s registrar_id reports it (IANA ID or registry-specific ID alike), 1 or more. When set, returns domains registered at this registrar on the given date (paginated). |
Input schema (JSON)
{
"additionalProperties": false,
"properties": {
"date": {
"description": "Date to search for registrar clusters (YYYY-MM-DD format), a UTC day: registrations from 00:00 to 24:00 UTC. When omitted, the most recent UTC day (within the last 7) with a normal volume of registrations is used, the same day for every page, and the response says which.",
"maxLength": 10,
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"type": "string"
},
"limit": {
"description": "Summary mode: registrar clusters, default 25, max 80 (up to about 700 bytes each). Detail mode: domains per page, default 200, max 500 (about 100 bytes each). Larger values are capped; 0 or less is the default.",
"type": "integer"
},
"min_cluster_size": {
"description": "Summary mode only: minimum number of domains a registrar must have registered on that date to be included, 2 or more, default 8. Higher values (50, 100, 500) keep only large bulk campaigns. Refused with registrar_id.",
"type": "integer"
},
"offset": {
"description": "Detail mode only (registrar_id set): domains to skip (alphabetical order), from a previous response's next_offset, default 0; a negative offset is refused. A nonzero offset is refused in summary mode, which has no pages.",
"type": "integer"
},
"registrar_id": {
"description": "Registrar identifier to drill into, exactly as a summary row's registrar_id reports it (IANA ID or registry-specific ID alike), 1 or more. When set, returns domains registered at this registrar on the given date (paginated).",
"type": "integer"
}
},
"required": [],
"type": "object"
}Generated from the live server (DataPulse MCP v0.9-341-g27163c2) on October 20, 2026.