Domain Verification

​

How verification works

​

The flow

1. Register — POST /domain with your domain. The response includes the complete dns record set immediately, so you can add everything in one DNS session.
2. Add the records at your DNS provider.
3. Verify — POST /domain/{id}/verify, or watch GET /domain/{id}/dns update live as records propagate.
4. Done — on completion your noreply@yourdomain sender is created automatically and campaigns can send from your domain.

​

Live status for every record

{
  "sendReady": false,
  "verificationStates": {
    "domain": "Verified",
    "spf": "NotStarted",
    "dkim": "VerificationFailed",
    "dkim2": "NotStarted",
    "dmarc": "NotStarted"
  },
  "records": [
    {
      "type": "CNAME",
      "host": "selector1._domainkey",
      "value": "selector1-....azurecomm.net",
      "verification": "VerificationFailed",
      "conflict": {
        "reason": "A CNAME already exists at selector1._domainkey pointing to \"selector1.mailprovider.example\" (likely a previous email provider).",
        "resolution": "Edit ONLY the CNAME at \"selector1._domainkey\" from \"selector1.mailprovider.example\" to \"selector1-....azurecomm.net\" — change nothing else.",
        "actions": [
          {
            "action": "edit",
            "type": "CNAME",
            "host": "selector1._domainkey",
            "currentValue": "selector1.mailprovider.example",
            "newValue": "selector1-....azurecomm.net"
          }
        ]
      }
    }
  ],
  "fixes": [
    "DKIM Record 1: Edit ONLY the CNAME at \"selector1._domainkey\" from \"selector1.mailprovider.example\" to \"selector1-....azurecomm.net\" — change nothing else."
  ]
}

​

Conflict detection — when a record “won’t verify”

• Two SPF records — multiple v=spf1 records make SPF fail entirely. We compute the exact merged record to publish, tell you which record to keep and edit, and name the specific record(s) to delete — everything else in your DNS is left alone.
• Existing SPF without our include — never add a second SPF record; we return the merged value to edit into your existing one.
• DKIM name occupied — a previous email provider’s CNAME (edit it to our value) or an old TXT key squatting the selector name (delete only that TXT, then add the CNAME).
• Existing DMARC — informational only; your existing policy is fine.

​

Tips

• Your registrar may show the host as selector1._domainkey or selector1._domainkey.yourdomain.com — both are the same record.
• SPF and Ownership both live at @ (the domain root) as TXT records — they coexist fine; only a second v=spf1 record is a problem.
• DNS changes usually propagate in minutes but can take up to an hour depending on your provider’s TTL.