Hosting and registration history
Two tools give a domain’s past, from two different sources:
datapulse_dns_dphistory: the dated versions of its web, mail and nameserver providers, from the DataPulse names corpus.datapulse_dns_rdap_history: the RDAP observations DataPulse has taken of it (registrar, abuse contact, status, nameservers, dates).
The first records listing events in the corpus; the second records what the registry published. Reading the two together is covered at the end of this topic. Paging fields, found: false answers and input canonicalization follow datapulse_help(topic="conventions").
datapulse_dns_dphistory
What the data is
For every listed name the corpus keeps one record: the providers of four services (see Service types). The history is the change log of that record, not a series of snapshots.
- The log begins on 2023-04-07, the initial snapshot. Every domain listed then has an
aon that day. Nothing earlier exists. - A version is written only when the record changes. A domain whose setup never changed has a single version, however popular it is (microsoft.com has one).
- Changes land mostly on the first of a month from 2024 on. A first listing (
a) can fall on any day. Expect month granularity when dating a change. - It holds no DNS records. Web hosting appears only as the ASN of the address the site resolves to, so CDN use is visible as an ASN (13335 for Cloudflare), not as a CNAME chain. There are no A, AAAA, CNAME, TXT or registrar data and no ASN operator names or countries.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | The name to ask the corpus about. No labels are removed: www.github.com and github.com are separate lookups |
limit | integer | No | Versions per page: default 40, max 60 (larger values are capped, 0 or less is the default); about 1 KB each |
offset | integer | No | Versions to skip, oldest first, from next_offset |
Versions is paged oldest first, so the same offset always returns the same versions. Most names fit one page: amazon.com has 34 versions and akamai.com 36 (2026-10).
Which names are listed. Corpus entries are registrable domains and names under registry-run private suffixes; names under platform suffixes vary name by name, so a live site can still answer found: false. The rule and its examples: datapulse_help(topic="methodology").
Response
{
"query": "github.com",
"datetime": "2026-09-16T22:11:02.84Z",
"server_id": "bonsearch-1",
"results": {
"Name": "github.com",
"Versions": [
{"YMD": 20230407, "Type": "a", "Body": {"name": "github.com", "services": [...]}},
{"YMD": 20260401, "Type": "c", "Body": {"name": "github.com", "services": [...]}}
]
},
"complete": true,
"found": true,
"total": 2, "returned": 2, "offset": 0, "truncated": false
}
| Field | Meaning |
|---|---|
query | The canonical name that was looked up |
submitted_domain | The input, present only when canonicalizing changed more than letter case |
datetime, server_id | Describe this API response, not the domain |
results.Name | The corpus entry’s name |
results.Versions | The timeline, oldest first |
complete | false when the server truncated the timeline |
found | true when the corpus has the name |
error | The API’s own error for this name, when it reported one |
total, returned, offset, truncated, next_offset, note | Paging; note also explains a found: false |
A name the corpus never listed is answered, not errored, in one of two shapes: the API’s envelope with found: false, an empty Versions and a note; or, when the reply carried no entry for the name at all, {domain, found: false, detail?, note}, where detail is the API’s reason when it gave one.
Version types
Type | Meaning |
|---|---|
a | First listed: the domain began passing the active-and-functioning check. Also the entry, dated 20230407, for every domain in the initial snapshot |
c | The record changed from the previous version. The Body is the full record as of that day, not a diff: the change is the difference between consecutive versions |
d | De-listed: the domain stopped passing the check and left the corpus; services is empty. A later a is a re-listing. The version before a d may still show services: the check failed on something the record does not show, most often the delegation |
These are listing events, not registry events. a is not a registration date; it is when the name first passed the corpus quality gate. d is not a registry deletion; a de-listed domain is usually still registered. Registry-side events are in datapulse_dns_rdap_history; how listing is decided is in datapulse_help(topic="methodology").
Body
{
"name": "kevbo.org",
"services": [
{"type": "AW", "providers": [{"asn": 6181}]},
{"type": "MX", "providers": [{"name": ["postoffice-ipv4.kevbo.org"], "asn": 6181}]},
{"type": "OperationalNS", "providers": [{"name": ["aron.ns.cloudflare.com", "quinton.ns.cloudflare.com"], "asn": 13335}]},
{"type": "ReportedNS", "providers": [{"name": ["aron.ns.cloudflare.com", "quinton.ns.cloudflare.com"], "asn": 13335}]}
]
}
servicesis always an array: empty for everyd, and for acwhose services all vanished (a de-listing in progress; thedfollows on the next cycle).providers[].namelists the hostnames grouped under one provider, case-folded. It is absent forAW, which is an address.providers[].asnis the provider’s autonomous system number as a flat integer, absent when unknown.- A Body the API sent that is not a record is passed through as
body_raw, withbody_errorsaying why it did not decode.
Service types
| Type | Description |
|---|---|
AW | Web hosting: the ASN of the address the www hostname resolves to, or the apex when there is no www |
MX | Mail exchangers |
OperationalNS | Nameservers that actually answer authoritatively for the name |
ReportedNS | Nameservers delegated by the parent zone (the NS set held at the registry) |
OperationalNS and ReportedNS normally agree. When they differ, the delegation and the zone’s own NS set have diverged: a nameserver migration in progress, or a stale delegation.
Example: kevbo.org
Four versions, condensed to what changed:
| YMD | Type | AW | MX | NS (both) |
|---|---|---|---|---|
| 20230407 | a | 10796 | mail-ipv4.kwhite.net (63949) | gandi.net (209453) |
| 20240405 | c | 10796 | mail-ipv4.kwhite.net (63949) | ns.cloudflare.com (13335) |
| 20241001 | c | 6181 | mail-ipv4.kwhite.net (63949) | ns.cloudflare.com (13335) |
| 20251001 | c | 6181 | postoffice-ipv4.kevbo.org (6181) | ns.cloudflare.com (13335) |
Listed in the initial snapshot on Gandi nameservers; nameservers moved to Cloudflare by 2024-04-05; web hosting moved from AS10796 to AS6181 by 2024-10-01; mail moved onto the same AS6181 host by 2025-10-01. Each c carries the whole record, so the change is whatever differs from the version before it.
Example: a de-listing (fyrios.com)
"Versions": [
{"YMD": 20260104, "Type": "a", "Body": {"name": "fyrios.com", "services": [
{"type": "AW", "providers": [{"asn": 13335}]},
{"type": "OperationalNS", "providers": [{"name": ["ns-cloud-d1.googledomains.com", "..."], "asn": 15169}]},
{"type": "ReportedNS", "providers": [{"name": ["ns-cloud-d1.googledomains.com", "..."], "asn": 15169}]}]}},
{"YMD": 20260201, "Type": "c", "Body": {"name": "fyrios.com", "services": []}},
{"YMD": 20260301, "Type": "d", "Body": {"name": "fyrios.com", "services": []}}
]
Listed on 2026-01-04 with no mail; by 2026-02-01 nothing answered (the c with empty services); on 2026-03-01 it left the corpus. Removal is confirmed on the cycle after the services vanish, so a domain can sit listed with an empty record for about a month. datapulse_help(topic="why_missing") pairs this arc with the RDAP history to find the registry-side reason.
Known noise
Not every c is a change the operator made.
- Anycast ASN churn. The same nameserver or MX hostnames are attributed to a different
asnfrom one month to the next, because the address measured sits in an anycast or multi-homed network.co.uk’s nameservers wander among five ASNs with no nameserver change; bbc.co.uk’s MX hosts flip between AS16509 and AS396982. Hostnames are the stronger signal. An ASN-only difference with the same hostnames is a move only if it persists and the hostnames eventually change too. - One host, two ASNs. The same MX hostname can appear twice in one version under different ASNs when its addresses were measured in two networks. It is one mail provider.
- The 2025-09-01 collection gap. Domains on Google Workspace mail (github.com, gfycat.com, hotbit.io and others) lost their
alt1–alt4aspmx.l.google.comhosts on 20250901 and regained them on 20251001: two spuriouscversions per affected domain. - A
cwith empty services is a de-listing in progress, not a configuration change. - Listing flap. A domain can alternate
d/amonth after month with the same providers throughout: microsoft.jp.net was de-listed and re-listed four times between 2025-12 and 2026-08. Such a run is one unstable delegation, not repeated outages and migrations, and its individualaanddentries date nothing.
datapulse_dns_rdap_history
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | The domain. It is reduced to its registrable domain under the full Public Suffix List, private suffixes included: www.bücher.com. is looked up as xn--bcher-kva.com, www.microsoft.jp.net as microsoft.jp.net. An underscore in the registrable domain is refused; _dmarc.example.com is looked up as example.com |
limit | integer | No | Observations per page: default 50, max 90 (larger values are capped, 0 or less is the default); about 650 bytes each |
offset | integer | No | Observations to skip, in the API’s order, from next_offset |
Response
The DataPulse API’s RDAP envelope with paging added. results holds the observations in the API’s order (newest first; researchdate says when each was taken), so results[0] is the newest scheduled crawl. Crawls are sparse, a few a year for a typical domain, and the newest can be weeks old: datapulse_live_rdap gives the current state, and a live lookup with force=true adds no observation here.
{
"query": "/dpdb/v1/rdap/etauk-gov.com",
"datetime": "2026-09-16T14:23:33.859720623Z",
"server_id": "alpha03",
"results": [
{
"name": "etauk-gov.com",
"researchdate": "2026-03-29T09:30:09.331513107Z",
"ianaid": 625,
"registrationdate": "2025-04-27T13:41:40Z",
"expiration_date": "2027-04-27T13:41:40Z",
"last_changed": "2026-03-25T13:22:29Z",
"status": ["client transfer prohibited"],
"dns": ["ns1cmt.name.com", "ns2fgp.name.com", "ns3cpr.name.com", "ns4cfn.name.com"],
"abuse_email": "abuse@name.com",
"abuse_phone": [{"type": "voice", "value": "tel:7202492374"}]
}
],
"total": 2, "returned": 1, "offset": 0, "truncated": true, "next_offset": 1,
"note": "..."
}
query, datetime and server_id describe this API response (the request path, when it was answered, which API node answered), not the domain. name, dns, status and registrant_cc are case-folded; every list stays in the order the API sent it.
| Field | Type | Description |
|---|---|---|
name | string | The domain |
researchdate | string | When DataPulse captured this observation |
ianaid | integer | IANA registrar ID, resolved by datapulse_dns_registrar; 0 and other registry numbering: “Registrar identifiers” in datapulse_help(topic="infrastructure") |
abuse_email | string | Registrar-published abuse email |
abuse_phone | array | [{type, value}], value a tel: URI |
dns | array | Nameservers reported in RDAP |
status | array | EPP status codes, e.g. client transfer prohibited (meanings: datapulse_help(topic="rdap")) |
registrationdate, expiration_date, last_changed | string | RFC 3339 dates as of that observation; the same names datapulse_live_rdap uses |
registrant_cc | string | Registrant country code, when the registry publishes one |
error | string | Present when DataPulse’s own RDAP lookup failed that day |
An entry with error is a failed collection, not a fact about the domain: its registration fields are empty, so skip it when diffing. Failures are marked by error alone, not by ianaid 0, which every successful observation under a registry without IANA IDs also carries.
An empty results array is the API’s “known name, no data” answer and is returned as it came. A domain the API has never observed answers {domain, found: false, detail?, note}, with detail the API’s reason when it gave one; names under registries without RDAP look the same. There is no registrant contact data: see datapulse_help(topic="rdap").
Reading it
- Registrar transfers: diff
ianaidbetween consecutive successful observations; a change means the domain moved between the two crawls. - Abuse-contact provenance: when a complaint names an
abuse_emailorabuse_phonethat live RDAP no longer shows, the observations show when it changed and what it was. Transfers usually rotate the abuse contact at the same time. - Holds and locks:
statusandlast_changedacross observations date when a hold or lock was added or removed;datapulse_help(topic="why_missing")walks through the traps.
Pairing the two timelines
The corpus history shows nameserver, web-hosting ASN and MX changes, dated to listing cycles; the RDAP history shows registrar, abuse-contact, status and date changes, dated to crawls. Querying both for one domain gives a two-track timeline: a registrar transfer accompanied by a nameserver and hosting overhaul reads very differently from a routine nameserver swap, and an a → c (empty) → d arc in the corpus next to a new client hold in RDAP explains a de-listing (the fyrios.com case). The two run on different schedules, so match events by period, not by day.
Generated from the live server (DataPulse MCP v0.9-341-g27163c2) on October 20, 2026. Your AI assistant reads this page by calling datapulse_help(topic="history").