Link domains must not appear in threat intelligence

The requirementstatement

Domains appearing in message content must not be flagged by threat-intelligence sources.

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: campaign.sample[] link domains
Where it liveslayer: Message contentMESSAGE_CONTENT
How Ekas settles itdetectability: AI · formAI_FORM; A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
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: CTIAT-MobileTwilio
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Carriers screen destinations against reputation databases, so a link to a compromised or previously-abused domain gets the campaign filtered regardless of how clean the registration is. Shared hosting and recycled domains are the usual innocent cause.

How to fix itremediation

Check every domain you link against Google Safe Browsing and VirusTotal before registering, and move off any flagged host. A previously-abused domain will not clear simply by waiting.

Check this yourselfattestation

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

Is every domain you link to in these messages clean on Google Safe Browsing and VirusTotal today?

1List the domains in the sample messages, including link-shortener destinations.
2Check each against Google Safe Browsing and VirusTotal.
3Move off any flagged host — a previously abused domain will not clear simply by waiting.

What wrong looks like: A recycled domain or a shared host carries somebody else's history into your campaign, and the traffic is filtered regardless of how clean the registration is.

Notesnotes

Needs a reputation lookup the product does not have; surfaced as a warning with the check the user should run themselves.

Rules you will hit next

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

MSG-008Opt-in confirmation must be 20–255 charactersBlockingBLOCKING MSG-009HELP reply must be 20–255 charactersBlockingBLOCKING MSG-011Opt-out confirmation must be 20–255 charactersBlockingBLOCKING MSG-018An MMS campaign must attach at least one sample media fileBlockingBLOCKING MSG-019Each MMS sample file must sit under its per-type size ceilingBlockingBLOCKING MSG-031Sample messages must be in EnglishBlockingBLOCKING

All message content rules

MSG-106 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.