Network

Autonomous System

ASN

AS199154

Network

AIRDRESS

IPv4 prefix

185.43.32.0/24

IPv6 prefix

2a14:ae00:101::/48

Points of Presence

Custom domain targets

Your own domain, in front of an airdress. These are the records to create, and they are the same ones your account shows you when you add a hostname. In the examples below app.example.com stands for your hostname and example.com for a zone apex. Both point at your airdress's own name, shown as <your-airdress>.a.airdr.es below; your account shows the exact name.

• CNAME is the recommendation for a hostname.
• ALIAS is the recommendation for an apex. Your provider may call this ALIAS, ANAME, or CNAME flattening. Required at a zone apex, where a plain CNAME is not allowed. These resolve when the query is made and follow the target, so they track a move without you touching your zone.
• A is the fallback when a provider offers neither. Works, but does not follow a future address change. Prefer CNAME or your provider's ALIAS / flattening feature.

Verification

Adding a hostname issues a token, published as a TXT record on _airdress-verify.example.com with the value airdress-verify=<token>. Leave this record in place. A fresh value is issued every 30 days and checked; removing it stops the hostname routing.

Certificates

A hostname on DNS-01 alias mode — which is how a wildcard is issued — also takes a CNAME from _acme-challenge.example.com to _acme-challenge.<your-airdress>.a.airdr.es. That lets the certificate be issued without another record in your zone each time it renews.

If your zone publishes CAA records, allow pki.goog and letsencrypt.org, or certificate issuance for this hostname will fail.

These addresses are stable

185.43.32.11 is published as a customer target and does not renumber on our schedule. If it ever has to change, the change is announced 90 days ahead — on the status page and by email to every account holding a custom hostname — and the old address keeps answering for the whole notice period. A CNAME or an ALIAS follows us inside its TTL and needs nothing from you; a literal A record is the one that needs a hand, which is why the notice exists.

No IPv6 target is published yet, and ips.json carries an empty ipv6 array to say so. A CNAME or a flattened apex already answers over IPv6, because it follows the target's own records. The literal we would publish here is a relay address that the relay does not yet answer on, and we will not ask anyone to publish an address that does not answer. It appears here, and in the JSON, when it does.

Machine-Readable Formats

• /ips — plain-text list of IP ranges, one CIDR per line
• /ips.json — structured JSON with prefixes, PoPs, and metadata

Peering

Airdress maintains an open peering policy. Network details are published on PeeringDB.