# DNS connect - human pass-through and fail-open - Agent Delivery Network | Agent Delivery Network

<!-- adn:geo-lead -->
> DNS connect is ADN’s primary onboarding path. Visitors point public DNS at ADN; ADN terminates TLS on **Cloudflare for SaaS** and proxies traffic to your configured **HTTPS origin*

<!-- /adn:geo-lead -->

Back to Help DNS connect is ADN’s primary onboarding path. Visitors point public DNS at ADN; ADN terminates TLS on Cloudflare for SaaS and proxies traffic to your configured HTTPS origin .
## What ADN does for humans
 • Transparent pass-through - ordinary browser traffic is proxied to your origin without classification, rate limits, or policy blocks.
 • No credential logging - ADN does not log Cookie , Authorization , or request bodies on the human pass-through path.
 • Discovery tags only - on anonymous GET HTML responses (no Cookie or Authorization ), ADN may stream lightweight agent discovery tags using HTMLRewriter. Non-HTML bodies are streamed unchanged.
 • Fail-open - if ADN cannot load domain configuration (KV or database errors), ADN falls back to a straight proxy to your saved origin URL so the site stays up.
## What ADN does for identified agents
 Machine and bot traffic that ADN can identify (verified bots, agent tokens, known agent user agents) is still inspected under your policy. Rate limits and blocks apply to that traffic class only, not to human visitors.
## Origin security
 • Origins must be HTTPS public hostnames that pass SSRF checks and your verification token (file or DNS TXT).
 • IP literal origins are rejected.
 • ADN sends a per-domain `x-adn-origin-auth` header your origin can allowlist (and `x-adn-origin-auth-previous` for 24 hours after rotation). Visitor-supplied IP forwarding headers are stripped; client IP is set from Cloudflare’s connecting IP.
 • You may keep your own WAF or CDN in front of the origin if you place your Cloudflare or CDN layer between ADN and the origin.
## Teardown grace period
 When you disable DNS connect in the dashboard, ADN shows DNS revert steps and keeps pass-through proxying for 14 days while you move DNS back to your provider. After grace ends, ADN removes the Cloudflare custom hostname and returns 503 with guidance if DNS still points at ADN.
## Apex and Cloudflare DNS
 • Enable apex on ADN in the dashboard to provision a second custom hostname with TXT DCV; then point apex DNS at the same ADN target (ALIAS/ANAME) for HTTPS 301 to www.
 • Without apex provisioning, use your registrar's HTTPS redirect from apex to www. Do not point apex at ADN without a certificate.
 • If your DNS is on Cloudflare , grey cloud (DNS only) is standard. Orange (proxied) is optional for orange-to-orange origins; use the Snippet connector if you need grey-cloud DNS only.
## Certificate pre-validation
 DNS connect uses TXT DCV so you can add ownership and certificate TXT records before cutover. When the dashboard shows Certificate ready , switch www DNS to ADN without a certificate error window.
## Compliance role
 For DNS connect, ADN acts as a processor of visitor traffic on your behalf while the hostname points at ADN. Human browser traffic is proxied; you remain controller for your site content and origin policies. Configure noindex on your origin if the deployment hostname should not be indexed separately from your public site.
 Ask ADN