Cloudflare accounts
How Cloudflare account context affects Axalot tracking domains, nameservers, headers, and health checks.
Console path
Console / Tracker / Domains
What Cloudflare controls
Cloudflare can control DNS routing, nameservers, proxy behavior, and response headers for a tracking domain. Axalot stores Cloudflare-related status so operators can see whether the domain is routed as expected.
Checks to understand
| Check | Meaning |
|---|---|
Cloudflare ID | Domain is associated with a Cloudflare record when available. |
Cloudflare headers | The domain response shows expected Cloudflare handling. |
Expected NS | Nameservers Axalot expects for the domain. |
Current NS | Nameservers currently visible for the domain. |
Setup workflow
Add or connect the domain in Axalot.
Confirm which Cloudflare account should own the domain.
Set the registrar nameservers to the expected Cloudflare nameservers.
Wait for DNS propagation.
Check NS valid, Alive, and Cloudflare headers.
Wrong account symptoms
If nameservers look correct but Cloudflare headers or health checks fail, confirm the domain is in the intended Cloudflare account and not an older account.