---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/30853#article
headline: "30853: Verification rejection - Disallowed - Phishing"
url: https://www.twilio.com/docs/api/errors/30853
inLanguage: en
dateModified: 2026-05-01T15:41:06.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 30853: Verification rejection - Disallowed - Phishing

Log Type: APPLICATION

Log Level: ERROR

## Description

Your verification submission was rejected because the business or message content was associated with a known phishing campaign. Messaging traffic on the phone number is blocked, and phone numbers must be verified before they can send messages to the United States and Canada.

### Possible causes

* The business or message content in the submission was identified as associated with a known phishing campaign.
* The review raised compliance concerns after evaluating the sending business, stated use case, sample content, web presence, opt-in or consent flow, and associated terms and privacy information.

### Possible solutions

* If you believe this rejection is incorrect, contact Support and provide additional information that clearly explains your business and messaging use case.
* Review the rejected verification in Console under the number's Regulatory Information tab so you can confirm the rejection details before you take next steps.
* Verify that the information in your verification record accurately represents your business and use case, including fields such as `BusinessWebsite`, `UseCaseSummary`, `ProductionMessageSample`, `OptInType`, and any supporting opt-in evidence or additional information.