The contact email domain must be provably the brand's

The requirementstatement

The brand contact email must be on a domain the business demonstrably owns — shown on its website, matching WHOIS, or verified by DNS.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: brand.business_contact_email domain
Where it liveslayer: BrandBRAND
How Ekas settles itdetectability: AI · crawlCRAWLExternal recordEXTERNAL_DATA; Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass.
What the fix involvesfailureClass: Fix the fieldRETRY_FIELD; A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities: TwilioTCR
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Authentication+ sends a PIN to this mailbox and treats whoever answers it as the business, so domain ownership is the thing being verified rather than a formality about tidy addresses. A domain that appears nowhere on the brand's own site cannot be tied back to it, and the verification is refused rather than delayed.

How to fix itremediation

Use a mailbox on the same domain as the registered website, and make sure that domain appears as a contact address somewhere on the site. Where the business uses a different mail domain, publish it on the site's contact page before submitting. Done when the domain in the email can be found on the brand's own website.

A compliant exampleexample

business_contact_email: jane.doe@acmecoffee.com · website: https://acmecoffee.com

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twilio	21736	Yes

Check this yourselfattestation

Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.

Can the email domain on this brand be found on the brand's own website?

1Open the registered website and look for an address on this domain — the contact page is where a reviewer looks.
2Where the business uses a different mail domain from its website, publish it on the contact page before submitting. That is the cheapest way to establish ownership.
3Authentication+ sends a PIN to this mailbox and treats whoever answers it as the business, so the domain is the thing being verified.

What wrong looks like: A mail domain that appears nowhere on the site cannot be tied back to the business, and the verification is refused rather than delayed.

Notesnotes

Absorbs BRD-118, which is the same ownership requirement stated for the Auth+ flow. Recommended universally and mandatory for public companies. The crawl can tell us whether the domain appears on the site; WHOIS and DNS TXT verification are external, so where the site does not show the address the user has to establish ownership another way — usually by publishing it on the contact page, which is also the cheapest fix.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

BRD-001A legal company name is required for every entity but a sole proprietorBlockingBLOCKING BRD-002Legal name must match the IRS record for the EINBlockingBLOCKING BRD-003Legal name must carry its exact entity suffix as filedBlockingBLOCKING BRD-008Legal name must not carry an appended personal name or roleBlockingBLOCKING BRD-009The legal name field takes the legal name, not the trading nameBlockingBLOCKING BRD-011A legal business name may back only one brand across the whole registryBlockingBLOCKING

All brand rules

BRD-111 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.