← All guides

Domains and email guide

Attach a domain now; search and checks have a controlled provider foundation

AnchorScape treats a domain as production configuration. The Cloudflare connector can provide suggestions and authoritative availability checks when configured; purchasing remains disabled until ownership, billing, renewal and irreversible-action confirmations are complete.

Result: A verified custom domain attached to the correct production environment, with clear ownership and email responsibilities.

Use a domain you already own

  1. 1Open Console → Environments and select the production environment.
  2. 2Add the custom domain and copy the exact DNS record AnchorScape displays.
  3. 3Create that record at the current DNS provider.
  4. 4Return to the environment and choose Verify domain.
  5. 5Wait for TLS, then test HTTPS, redirects and application routes before changing user traffic.

Domain registration control path

  • Cloudflare domain suggestions followed by an authoritative real-time availability check.
  • Price and renewal terms shown immediately before purchase.
  • Explicit purchase confirmation, idempotency and a complete audit trail.
  • Registrant ownership kept separate per client, followed by DNS and TLS attachment.
  • Renewal, expiry and failed-payment alerts without silently transferring ownership to AnchorScape.
Cloudflare Registrar is the preferred first connector for supported TLDs because DNS, TLS and security policy remain cohesive. It does not cover every regional TLD, so AnchorScape needs a second registrar connector rather than provider lock-in.

Email choices

  • Mailbox hosting: integrate a managed provider that supplies SMTP, IMAP, spam controls and account administration.
  • Forwarding only: Cloudflare Email Routing can forward inbound addresses when Cloudflare is authoritative for DNS.
  • Application email: configure a transactional mail provider as an environment secret and verify SPF, DKIM and DMARC.

Need help on the screen?

Open Anchorton and ask where a setting belongs. For runtime questions, open it from the deployment context so it can use the permitted status, event and log tools.