Hosting shared with malicious neighbours is scored against the domain

JSONMarkdown

The requirementstatement

A domain resolving to an IP or ASN shared with known-malicious sites carries that reputation into the brand score.

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
resolved IP and ASN neighbours
Where it liveslayer
WebsiteWEBSITE
How Ekas settles itdetectability
External recordEXTERNAL_DATA
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
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
Twilio
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Reputation is assessed at the address as well as the name, so a business on cheap shared hosting inherits whatever its neighbours did. Nothing about the business causes it and nothing on the site reveals it, which makes it one of the hardest findings to act on — the brand looks clean from every angle the operator can see.

How to fix itremediation

Where vetting repeatedly stalls with no finding on the content, move the site to a dedicated IP or a reputable host and re-submit. Done when the domain resolves to an address whose other tenants you can account for.

Provider rejection codescodes

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

ProviderCodeResubmit
Twiliogen230961Yes

Check this yourselfattestation

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

Does this domain share its IP address with sites you cannot account for?

  1. 1Run a reverse-IP lookup on the domain.
  2. 2Hundreds of unrelated sites on the same address is the signal — cheap shared hosting inherits whatever its neighbours did.
  3. 3The only fix is moving to a dedicated IP or a reputable host, then resubmitting.

What wrong looks like: Vetting stalls repeatedly with no finding on the content. Nothing about the business caused it and nothing on the site reveals it, so the brand looks clean from every angle the operator can see.

Notesnotes

We resolve no addresses and hold no reputation feed. The user can check this themselves with a reverse-IP lookup on their domain: if it shares an address with hundreds of unrelated sites, that is the signal, and changing host is the only fix.

Rules you will hit next

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

WEB-004The website value must fit the provider field limitMediumMEDIUMWEB-006The website should sit on a custom domainMediumMEDIUMWEB-015Pages the registration points at must not be brokenMediumMEDIUMWEB-044The footer should carry a phone number, an email and a street addressMediumMEDIUMWEB-054A brand with a website must publish its policies as web pages, not as PDFsMediumMEDIUMWEB-074Pages must not load sub-resources over HTTPMediumMEDIUM

All website rules

WEB-083 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