Authoritative DNS & network intelligence

Resolve fast. Know the network you resolve into.

ASNDNS runs authoritative DNS on an anycast edge with geo-steering and health-checked failover — and exposes the ASN, prefix and BGP data behind every answer through one JSON API. Built for engineers who read packet captures for fun.

Anycast resolution · DNSSEC · RFC 2136 dynamic updates · Terraform provider

Try a lookup

Live data

Enter a domain, IP address or AS number. This queries the same API and the same dataset a paying client gets — nothing here is mocked.

GET /v1/lookup?q=1.1.1.1
What you get

Two halves of the same problem

Geo-steered answers

Route by continent, country, subdivision or client ASN. Weighted pools split traffic in fractions you set, and every rule is a plain record in the zone — no side console.

Health-checked failover

HTTP, TCP and ICMP probes from multiple regions. A pool that fails consensus is withdrawn from answers within one TTL, and returns only after it holds healthy.

Network intelligence API

ASN, prefix, RIR allocation, reverse lookups and announced address space — one JSON endpoint, one token, cursor pagination, no per-field surcharge.

Edge-native control plane

The API and dashboard run at the edge, so a record change propagates from wherever you called it. Zone files, Terraform and REST all write to the same state.

From your Worker

One fetch, one token, typed JSON

Enrich a request with the client's ASN before you decide how to serve it — inside the same edge runtime, without leaving the request path. Rate limits are per token and returned in headers.

Read what the API returns →

export default {
  async fetch(request, env) {
    const ip = request.headers.get("cf-connecting-ip");

    const r = await fetch(
      `https://api.asndns.com/v1/ip/${ip}`,
      { headers: { authorization: `Bearer ${env.ASNDNS_TOKEN}` } }
    );

    const { asn, holder, prefix, country } = await r.json();
    // asn: 13335 · holder: "CLOUDFLARENET" · prefix: "1.1.1.0/24"

    return Response.json({ routedFor: asn, holder, prefix, country });
  }
};

Move a zone this afternoon

Import an existing zone file or AXFR from your current provider, verify answers side by side, then cut the NS records over when the diff is clean.

Products

Two services, one control plane

Managed authoritative DNS and the network-intelligence API share one account, one token scope model and one audit log. Use either on its own; they compose when you use both.

Authoritative DNS

Managed DNS hosting

Anycast nameservers answer from the nearest edge location. Records, pools and steering rules are versioned, and every change is diffable before it ships.

  • DNSSEC signing with automatic key rollover
  • Geo, weighted and failover answer pools
  • Secondary DNS in either direction (AXFR/IXFR)
  • RFC 2136 dynamic updates and zone file import
Network intelligence

ASN, IP & BGP API

Resolve an address to the network that announces it, then walk outward — allocation, registry, announced space and reverse records.

  • /v1/ip/{ip} — ASN, holder, covering prefix, PTR
  • /v1/asn/{asn} — RIR, allocation date, prefix counts
  • /v1/asn/{asn}/prefixes — full announced list
  • /v1/domain/{name} — records plus the network behind them

Supported record types

TypePurposeSteering
A / AAAAAddress records for IPv4 and IPv6 originsGeo, weighted, failover
CNAMEAlias onto another nameGeo, weighted
ALIASApex alias that resolves to addressesGeo, weighted, failover
MXMail exchangers with preferenceFlat
TXTSPF, DKIM, DMARC and domain verificationFlat
SRVService location with port and priorityWeighted
CAACertificate authority authorisationFlat
NS / DSDelegation and DNSSEC chain of trustFlat

How teams wire it up

Regional routing

Answer with the origin closest to the querying resolver, and fall back to a shared region when a pool drops out.

Peering-aware delivery

Look up the client ASN at request time and serve from the origin with the shortest path to that network.

Signup enrichment

Tag a new account with the network it registered from — hosting, mobile or residential — before it reaches your risk rules.

Pricing

Per zone, per query, no seats

Every plan runs on the same network. Paying more raises limits and adds operational features — it never buys you a faster answer.

Developer

$0 / month

For side projects and evaluation. Same anycast network as every other plan.

  • 3 zones
  • 1M DNS queries / month
  • 10k API requests / month
  • DNSSEC, geo steering, full API
Start free

Pro

Most chosen

$20 / month

For production services that need health-checked failover and higher volume.

  • 25 zones
  • 50M DNS queries / month
  • 500k API requests / month
  • Health probes, secondary DNS, audit log
Choose Pro

Scale

$200 / month

For platforms serving many customer zones through one account.

  • 500 zones
  • 1B DNS queries / month
  • 10M API requests / month
  • Bulk API, daily data snapshots, priority support
Choose Scale

Metered usage

MeterIncludedOver the allowance
DNS queriesPer plan allowance$0.30 / million
API requestsPer plan allowance$1.00 / 100k
Additional zonesPer plan allowance$0.50 / zone / month
Health check targets5 per zone$1.00 / target / month

Billing questions

What counts as a query?

One answered DNS question at an authoritative nameserver. Retries for the same question within the TTL are not counted twice.

What happens over the limit?

Answers keep being served. Overage is metered at the rates above and billed at the end of the cycle — resolution is never suspended for usage.

Can we leave?

Export every zone as a standard zone file at any time, from the API or the dashboard, with no notice period and no export fee.

Do you offer annual terms?

Yes, on Pro and Scale, billed once a year. Write to us with your zone count and query volume and we will quote it.

About

A small team, one layer of the stack

ASNDNS LLC is a California company building in one narrow place: the moment a name becomes an address, and everything you can learn about the network that address belongs to. We do not sell compute, storage or a bundle you have to grow into.

Documented before shipped

An endpoint reaches the public API only once its reference page, error codes and rate-limit behaviour are written down. No undocumented surface.

Your data leaves as easily as it arrives

Zones export as standard zone files and API results as plain JSON. Nothing is stored in a format only we can read.

Resolution is not a billing lever

Answers are served whether or not an invoice is open. Usage disputes are settled in email, not by withdrawing your records.

At a glance

Legal entityASNDNS LLC
JurisdictionCalifornia, United States
Founded2026
FocusAuthoritative DNS hosting and network intelligence data
Contactsupport@asndns.com
Contact

Write to a person

Technical questions reach an engineer, not a queue. Include the zone, the query volume or the API response you are asking about and you will get a specific answer.

Email

support@asndns.com — accounts, zones, API
abuse@asndns.com — abuse and takedown
billing@asndns.com — invoices and plans

Registered office

ASNDNS LLC
611 Wilshire Blvd
Los Angeles, CA 90017-2928
United States

Postal address for legal notice. Technical and billing matters are handled by email.

Send a message