The site must stay live for the whole vetting window, not just at submission

JSONMarkdown

The requirementstatement

The brand website must remain live and publicly reachable for the entire vetting period, which runs weeks after submission.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
brand.website over the review window
Where it liveslayer
WebsiteWEBSITE
How Ekas settles itdetectability
Post-submissionUNDETECTABLE_PRE_SUBMISSION
The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
What the fix involvesfailureClass
Wait on someone elseTERMINAL_EXTERNAL
Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities
AWSBandwidthKlaviyoPostscript
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Vetting re-fetches the site days or weeks later, so a site that was up when the form was filled in is not the thing being judged. The named failure is a password-protected storefront: a shop put into maintenance mode for a redesign, or a trial plan that lapses, takes the brand down with it and the rejection arrives with no hint that timing was the cause.

How to fix itremediation

Keep the site public and unchanged until the brand and campaign are approved. Do not schedule a migration, a password gate or a plan downgrade during the window; AWS states 10DLC review takes at least four to six weeks and toll-free three to ten business days.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Is any redesign, migration, password gate or hosting downgrade scheduled between now and approval?

  1. 1Ask whoever runs the site what is planned for the next six weeks. AWS states 10DLC review takes at least four to six weeks and toll-free three to ten business days.
  2. 2Hold the site public and unchanged until the brand and campaign are approved.
  3. 3Check any trial plan or hosting subscription that could lapse mid-review.

What wrong looks like: A shop is put into maintenance mode for a redesign three weeks after submission. Vetting re-fetches the site, finds a password-protected storefront, and the rejection gives no hint that timing was the cause.

Notesnotes

Nothing at submission time can settle this — the failure happens after we stop looking. Surfaced as a warning with the deadline: the user has to hold the site up, and to hold off any redesign or hosting change, until approval lands.

Rules you will hit next

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

WEB-018The site must be readable in EnglishHighHIGHWEB-026The site must look established rather than erected for the registrationHighHIGHWEB-028A campaign landing page is not the brand websiteHighHIGHWEB-030E-commerce brands need a published catalogHighHIGHWEB-032The business name must be visible on the page, not only in the markupHighHIGHWEB-039Contact details on the site must match the brand recordHighHIGH

All website rules

WEB-019 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works