Pages must not load sub-resources over HTTP

The requirementstatement

A page must not load sub-resources over, or redirect through, unencrypted HTTP — mixed content fails.

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
opt-in landing page
Where it liveslayer
WebsiteWEBSITE
How Ekas settles itdetectability
AI · crawlCRAWL
Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
What the fix involvesfailureClass
Fix the websiteTERMINAL_WEBSITE
The fix lives on your site. No amount of rewording the form clears it.
Who requires itauthorities
TCRTwilio
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Mixed content produces browser warnings on the exact page where a consumer is about to hand over a phone number, which undermines the trust the whole framework is built on. It also frequently signals an unmaintained site.

How to fix itremediation

Serve every asset over https and remove any http:// redirect hop in the chain to the opt-in page.

Notesnotes

Not decidable from a markdown-only fetch — needs the raw HTML and the sub-resource list. Recorded so the crawler gap is visible rather than silently unchecked.

Rules you will hit next

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

All website rules

WEB-074 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.