Map a domain's infrastructure

1. Where it points, and where it pointedCopy Anchor Link

domain_history gives a domain's current A and AAAA state, with the CNAME chain, and every answer it gave, oldest first.

curl https://api.ipalmanac.com/v1/domain/example.com/history \
  -H "Authorization: Bearer $IPALMANAC_API_KEY"

• current holds the latest state per record type: the values, the cnames chain, and whether it is stale.
• intervals holds each address with first_observed, last_confirmed and ended_at.

2. The networks it moved throughCopy Anchor Link

domain_hosting turns that history into runs: one per stretch of time the domain answered on one network (routing ASN and cloud, hosting or CDN provider).

curl https://api.ipalmanac.com/v1/domain/example.com/hosting \
  -H "Authorization: Bearer $IPALMANAC_API_KEY"

A move happened between one run's last_confirmed and its ended_at, never at an exact instant. A domain that leaves a network and comes back gets a new run.

Each run's network is today's ASN mapping and published ranges applied to the domain's addresses, not how they were routed at the time. So a run changes when the domain's addresses change, not when a network's ranges do.

3. What each network routesCopy Anchor Link

lookup_asn describes one network: its name and registry country, what kind of network it is, the IP ranges the mapping assigns to it, the published cloud, hosting and CDN ranges inside them, and how many IPs and domains we observed there.

curl https://api.ipalmanac.com/v1/asn/AS13335 \
  -H "Authorization: Bearer $IPALMANAC_API_KEY"

Its ranges are paged like any list; see Pagination.

Things to keep in mindCopy Anchor Link

• We resolve from one vantage point. A domain behind GeoDNS or anycast may answer differently where you are.
• The routing ASN comes from the IPtoASN mapping, not our own view of BGP, and it is not necessarily the holder of the addresses.
• History starts on October 1, 2026.