Yes. X can suspend an account for cold DMs, because its rules ban bulk messages nobody asked for. But a ban is rarely the first thing that happens. On the 46 customer accounts we ran from July to October 2026, the usual stop was the daily cap. Most days X showed its automation error came right after about 35 sends.
What X's rules say about cold DMs
X's automation rules say "You may not send unsolicited Direct Messages in a bulk or automated manner". The same page says you are "ultimately responsible" for what apps linked to your account do. So the rule covers people who send by hand at volume and every X DM automation tool, ours included.
X's spam rules repeat the ban on bulk DMs and add "sending identical direct messages" to the list.
There is one clear exception. Automated DMs are allowed when the person asked first, for example by messaging you, and you give them an easy way to opt out. Our page on what X allows when you DM many people shows how that route works.
What X does before a ban
X has a ladder of steps. The table runs from mildest to most severe, and its first row is X's daily cap rather than a penalty:
| What X does | How long it lasts |
|---|---|
| Refuses the next first message at your daily cap. | Until the 24 hour window rolls. |
| Asks for a phone or puzzle check. | Until you pass it. |
| Takes away a feature for a while, such as DMs. | X publishes no length. |
| Limits the account, so only followers see your activity. | The time stated in the notice. |
| Suspends the account. | Until an appeal works. Severe cases are permanent at once. |
For a first offence, X's spam rules say it may do anything from asking you to delete posts to "temporarily locking account(s)". If the problem is running several accounts, you may be asked to keep one while the rest are suspended.
That first row is X's cap on first messages to strangers, 7 a day on Free and 35 on Premium. The X DM limit, plan by plan explains when it resets.
What 46 customer accounts ran into
Our logs show refusals at the cap, a handful of checks and no suspensions. The table counts every send by the 46 X accounts we ran, from 2 July to 5 October 2026:
| What happened | Count |
|---|---|
| DMs X accepted. | 37,487. |
| Times X showed error 226, its automation warning. | 1,440, on 965 account days. |
| Error 226 days when the account had sent 33 to 37 that day. | 521 of the 965. |
| Accounts that got a phone or puzzle check at least once. | 9 of 46. |
| Accounts suspended. | 0. |
From 2 July to 5 October 2026, none of the 46 X accounts Xsender ran was suspended. 9 had a temporary phone or puzzle check. That is a record, not a promise. If X does suspend an account while our software runs it, our Refund Policy says "The charge for that month is refunded in full".
A 21 day study of 30 of those accounts, to 1 September 2026, made the pattern plain. All 23 Premium accounts that stopped at exactly 35 first messages got error 226 on the next try. The warning sounds like a verdict on you, but in our data it mostly meant the count was full.
Does sending the same message get you banned?
Not in our data, even though X's spam rules list identical DMs. Our users rotate a few templates across thousands of leads. The median campaign uses 5 message versions, and one version went out 8,058 times without a suspension.
Our numbers only cover first messages paced minutes apart, with names filled in per lead. We have not tested one identical line fired at hundreds of people in an hour, so read them as a record of careful sending, not a licence.
How to keep the risk low
Most of the risk sits in volume and speed, so the habits that lower it are about counting and pacing:
- Count to your cap. Track first messages per account over the past 24 hours, counted from this time yesterday.
- Send one message per lead. X lets one message into a pending request until the person accepts, so a follow-up cannot get through before that.
- Pick leads who can receive a DM. About 1 in 4 leads we tried had closed DMs, and collecting only profiles with open DMs avoids that.
- Space your sends. Our accounts wait 3 to 5 minutes between messages and spread the rest across the day.
- Stop after a check. If X asks for a phone number or a puzzle, pass it and rest the account for the day.
Xsender reads the cap X gives each account, stops one send short of it on normal days, and never retries a lead X refused. About once a week it sends one more, to check whether the account's plan has gone up.
FAQ
How long does a DM restriction on X last?
A refusal at the daily cap lasts until the 24 hour window rolls. On our accounts, the next send went through 24.7 to 27 hours after the batch began. A phone or puzzle check lasts until you pass it. A limited account stays limited for the time stated in X's notice.
Does error 226 mean a ban is coming?
Not on its own. Count the first messages the account sent since this time yesterday. If the count is at the cap, wait for the window to roll; if it is well under, stop every tool and send no new first messages until tomorrow.
Can X ban you for using a DM tool?
Yes. X's rules make you responsible for apps linked to your account, and they ban bulk unsolicited DMs however they are sent. How extensions, cloud tools and the API differ explains what each method risks.
Will X warn you before it suspends an account?
Not always. For a first offence, X's spam rules list steps up to a temporary lock. For severe cases, they say accounts "will be permanently suspended at first detection".
Try it on your own X accounts. See plans and the 7-day trial
Sources and method
Sources and dates
- The DM rule, the exception for people who asked first, and the line on linked apps: X's automation rules, updated April 2026, archived copy of 1 October 2026.
- Bulk and identical DMs, first offences and keeping one account: the spam section of X's Authenticity policy, archived copy of 23 September 2026.
- Limited accounts: X's locked and limited accounts page, archived copy of 21 September 2026. Every quoted line was checked again on X's live help pages on 5 October 2026.
- Caps by plan: X's help page on Chat, archived copy of 4 August 2026.
- Sends, error 226, checks, suspensions, templates and closed DMs: our logs for 46 accounts, 2 July to 5 October 2026.
- The 23 accounts at 35 and the reset timing: our 21 day study of 30 accounts, to 1 September 2026.
- The suspension refund: our Refund Policy, read 5 October 2026.