Verify a domain
Domain verification proves that you control a sending identity. It is required before Boundry accepts a From address on that domain.
Before you begin
Have access to your DNS provider—such as Cloudflare, Route 53, or your registrar—and decide which project should own the domain. A domain belongs to one regional project.
1. Add the domain to your project
Open Dashboard → Domains, choose Add domain, then select sending, receiving, or both. The regional Laravel API creates the identity immediately and generates the records for the selected capability.
{
"name": "mail.acme.com",
"capabilities": { "sending": true, "receiving": false }
}2. Publish the DNS records
Copy each record exactly from the dashboard. Boundry uses a branded BYODKIM selector and public key, and the SPF record includes Boundry’s regional policy hostname. The final MX target is shown exactly because it is a mail transport endpoint, not a cosmetic alias.
Domain verificationBoundry DKIMPublish the generated Boundry selector and public key.
Boundry AU deliverySPF / MXAdd the supplied records. Do not replace unrelated SPF entries.
Boundry AU inboundMX transportUse a dedicated subdomain unless you intend to route all company email here.
3. Verify and test
Back in the domain page, select Verify. The regional API performs a public DNS check locally; production SES also confirms the identity before it can send. DNS propagation can take a few minutes, sometimes longer depending on your provider.
curl -X POST https://api.au.boundry.dev/domains/dom_.../verify \
-H "Authorization: Bearer $BOUNDRY_API_KEY"Local mode is not a sending service. It persists records and checks public DNS, but it does not create an SES identity or send mail. The AU Laravel Cloud deployment does that after its regional SES credentials are configured.
Use a subdomain for inbound. Pointing the MX record of your root company domain at Boundry can disrupt Google Workspace or Microsoft 365 delivery.