The brand website is the root domain, not a page inside it
The requirementstatement
The brand website must be submitted as the root domain rather than a deep link or sub-path.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- brand.website
- Where it liveslayer
- BrandBRAND
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- 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
- Telnyx
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A reviewer given a specific page sees that page and nothing else, and a landing page or a product page rarely carries the business identity, the policy links or the contact details they are looking for. Registrants deep-link with the best intentions — usually to the signup page they are proudest of — and hand the reviewer the one view of the site that proves least.
How to fix itremediation
Put the site root in the brand website field. The opt-in page still gets cited — it belongs in the campaign message flow, where a deep link is exactly what is wanted. Done when the brand website is a bare domain with no path on it.
A compliant exampleexample
website: https://acmecoffee.com — with https://acmecoffee.com/checkout cited in the message flow instead
Notesnotes
The mirror of WEB-090, which asks the message flow to deep-link the opt-in page. The two fields want opposite things and for the same reason: the brand field proves the business exists, the flow field proves the consent surface does.
Rules you will hit next
6 other rules read brand.website. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
BRD-125The website URL must carry an explicit schemeBlockingBLOCKINGBRD-135A website may back only one brandBlockingBLOCKINGWEB-001A brand website URL is requiredBlockingBLOCKINGWEB-009The website must resolve and return contentBlockingBLOCKINGWEB-014Staging, admin and internal hosts must not be the brand websiteBlockingBLOCKINGWEB-004The website value must fit the provider field limitMediumMEDIUM
BRD-126 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.