Domains
How Axalot tracking domains are added, validated, monitored, and used by Tracker campaigns.
What domains do
Domains are the public hosts used in campaign tracking links. A campaign link is built from the selected domain, campaign track id, and Traffic Source parameters.
Tracking link host
Campaign URLs start with the selected domain.
Health checks
Axalot tracks whether the domain is alive and configured correctly.
NS validation
Expected nameservers are compared with current domain DNS.
Campaign dependency
A campaign needs a domain before it can generate a useful tracking link.
Console path
Console / Tracker / Domains
Domain format
Axalot accepts clean lowercase domains only.
| Rule | Example |
|---|---|
| Lowercase only | track.example.com |
| No protocol | use example.com, not https://example.com |
| No path, query, or fragment | use example.com, not example.com/path?a=1 |
| No trailing dot | use example.com, not example.com. |
| No IP address | use a domain name, not 192.168.1.1 |
| No numeric TLD | use a real top-level domain |
Paste only the hostname
If a browser URL contains https://, a path, query parameters, or a fragment, remove them before adding the domain.
Status fields
| Status | Meaning |
|---|---|
Active | Domain is enabled for use. |
Alive | Health check can reach the domain. |
Cloudflare headers | Response indicates expected Cloudflare handling. |
NS valid | Current nameservers match expected nameservers. |
RDAP data | Registration metadata such as registrar and expiration when available. |
Setup flow
Add or connect the domain in Tracker -> Domains.
Configure DNS at the registrar or Cloudflare according to the expected nameservers.
Wait for DNS propagation.
Check NS valid, Alive, and Cloudflare header status.
Select the domain on campaigns after the domain is healthy.
Types
| Type | Use when |
|---|---|
main | The domain is managed as a primary tracking domain. |
connect_existing | You connect a domain that already exists outside the current automated flow. |
Operational rules
- Keep one domain per clear traffic purpose or buyer group when practical.
- Do not use a domain in campaigns until DNS status is healthy.
- Keep notes for registrar, Cloudflare account, buyer, and launch context.
- Use tags to group domains by buyer, geo, source, or status.
- Check expiration data when RDAP information is available.