Verify your sending domain

Set up a recognizable sender such as hello@mail.example.com. Add mail.example.com to maxclicks, publish its DNS records and wait for Verified For Sending before using it for campaign, template, workflow or test email.

You need Write permission in the workspace and access to the DNS provider that manages the domain’s records. Use the records generated for your own domain; the demo below does not perform external DNS verification.

Why domains need verifying

Authentication establishes that maxclicks is authorized to send for your domain. It is required for sending from that identity, but it does not guarantee inbox placement. Reputation, audience quality and the receiving provider also matter.

A domain name already assigned to another workspace cannot be claimed again.

Add your sending domain

1. Open Settings → Domains. If you entered a domain during setup, open the existing row.
2. Otherwise choose Add domain and enter a domain, not a full email address.
3. Confirm the name. It cannot be renamed later; moving to a different name requires another domain.

Root domain or subdomain

A subdomain such as mail.example.com makes marketing sender configuration easier to manage separately. The app recommends it, while allowing the root domain too. It does not provide complete reputation isolation: Google’s compliance view includes subdomains under their primary domain. See domain choices.

Publish the DNS records

Open the domain’s verification dialog and copy each Name and Value to your DNS provider. Keep existing records used by your website or business mail.

Use the exact generated return-path name instead of assuming it is always send.. Some DNS providers append the domain automatically: check that the resulting full name does not contain your domain twice. If the provider rejects a record or one already exists at that name, ask the DNS owner to reconcile it.

Start verification and let the checks run

Choose Start verification check. Follow the individual statuses and the overall Verified For Sending result. The check continues asynchronously; DNS publication, caches and provider processing can delay it. A Pending state immediately after a change is not proof the values are wrong.

If verification does not complete, compare the exact record type, name and value with maxclicks. The presence of a record in your DNS dashboard is not the same as successful provider verification. Avoid repeatedly creating the domain.

Keep your records in place

maxclicks periodically rechecks verified domains. Removing the required records can remove verification and block subsequent sends. Restore the required records and inspect the current verification status before sending again.

Set your default domain

The first domain becomes the workspace default when added, before verification. The default does not bypass verification. You can Set as default on another verified domain; doing so also changes the default sender to a sender on that domain, or clears it when none exists.

Existing emails can retain an explicit sender. After verification, create the desired profile in Settings → Sender Profiles, then select it on the email itself and use Send test.

Sending rules that depend on verification

A verified domain is one prerequisite. A send can still be blocked by workspace sending status, consent, suppressions or available capacity. Read the actual reason rather than recreating a verified domain.

Deleting a domain also removes its sender profiles and can leave existing emails without a sender. Keep an old domain while active work still depends on it. Deletion can show Deletion queued or Deletion is waiting while the workspace remains closed for cleanup; those notices do not mean removal completed. Follow the displayed result before starting another sending change. See the domain reference for sender defaults, deletion and diagnostics.