Skip to content

Questions · Published 2026-09-29 · Updated 2026-09-29 · AgentiSend

How do I verify a sending domain on OVHcloud?

To verify a sending domain on OVHcloud, publish every required row from `GET /domains/{id}/setup` in the DNS zone, then call `POST /domains/{id}/verify`. The clicks below are OVHcloud's, fetched on 29 September 2026.

To verify a sending domain on OVHcloud, publish every required row from GET /domains/{id}/setup in the DNS zone, then call POST /domains/{id}/verify. The steps in the next section are the ones OVHcloud documents, fetched on 29 September 2026.

The records to publish

POST /domains registers the name. GET /domains/{id}/setup returns one row per record, with record, host, type, value, priority, and required. A TXT row also has value_strings and value_bind. Paste those. The DKIM value is the one on the row.

A new domain sends once the required rows resolve. Domains and DNS names them: the DKIM TXT, and the return-path MX and TXT. Root SPF and DMARC are recommended. A tracking CNAME is on the sheet only when tracking is available, and it never blocks verification. If host is @, that row is the apex. If the apex already has an SPF TXT, merge the sheet's value into that one record. A second SPF TXT on the same name invalidates both.

curl -sS -X GET https://api.agentisend.com/domains/9c8f8f0e-3d1a-4d3f-9a1e-2b7c1a0f5e42/setup \
  -H "Authorization: Bearer $AGENTISEND_API_KEY"
200
{
  "commands": {
    "cloudflare": [],
    "gcloud": [],
    "route53": {}
  },
  "deep_link": "example",
  "detected": false,
  "domain": "example",
  "nameservers": [],
  "provider": {
    "dnsConsoleUrl": "example",
    "id": "example",
    "name": "example"
  },
  "provider_hints": {
    "cloudflare": "example",
    "godaddy": "example",
    "namecheap": "example",
    "route53": "example"
  },
  "records": [],
  "zone": "example",
  "zone_file": "example"
}
Response

OVHcloud's dashboard, as of 29 September 2026

How to add a DNS TXT record says the zone is at Web Cloud, Domain names, the domain, DNS zone. Click Add an entry, select TXT, put the string in Value, and click Add. For a name that is not the apex, the same article says to fill Subdomain with the label only (as1._domainkey, not the full name) before Value. Editing an OVHcloud DNS zone says Add an entry also offers MX, and that a target which is a hostname must end with a dot or the zone name is appended. SPF records say an existing SPF may already be a TXT or an SPF type: edit that row rather than adding a second one, and a full v=spf1 string can be pasted as TXT. capturedOn: 2026-09-29.

Read it back

POST /domains/{id}/verify reports which required rows resolved. GET /domains/{id} is the sheet with each row's status.

Other registrars

Written by the AgentiSend team.