Zhenku
Guard · Verify

Binance's Anti-Phishing Code: What It Means, Which Codes Are Valid, and What It Can't Check

Zhenku Editorial · Cheng Mo Updated 2026-11-14 About 8 min
A guardian beast raising a gold shield against a fishing hook to protect a sealed envelope (cover illustration, AI-generated)

An anti-phishing code is a short string you set yourself in your Binance account; once it's on, Binance says it "will be included in all genuine e-mails and SMS from Binance," so a "Binance" message without it, or with the wrong one, may be phishing. The current format rules: 6 to 8 characters, at least three of uppercase letters, lowercase letters, digits and underscores, and no special characters (Binance Help Center, checked November 2026; the app's live prompt is the final word). It answers one question only — did this email or text really come from Binance. Calls, DMs and websites are outside its reach.

Two pairs of things tend to get blurred together. The first is "valid" versus "hard to guess": the help center lists format rules only and says nothing about checking how guessable a code is, and Binance1 meets every one of them. The second is two rule sets that both show up in search results — one from a 2022 Binance blog post, one from the current help center — and they don't even agree on length. Below, eight example codes go through both rule sets first; what makes a code hard to guess comes after that.

What it actually is: a signal between you and Binance

The code lives in your account's security settings. Once it's set, the emails and texts Binance sends you carry the string you chose — a private signal agreed between you and Binance. Real messages give the signal. Fakes can't. It doesn't encrypt or filter anything.

A scammer can copy the logo, the layout, the sender's display name, even a from-address that looks very close. What they can't copy is a string you picked in private. They don't know it, so a forged email either leaves it out or gets it wrong.

Why a fake email fails this check

A typical phishing email manufactures urgency ("unusual login detected," "withdrawal request awaiting confirmation," "your account will be frozen"), then pushes you to a link, a page that looks like Binance, and a form for your login, password and verification code. Step one of that chain is getting you to believe the email is real. That's the step the code blocks.

With it in place you stop squinting at from-addresses and check one thing: does this email claiming to be Binance carry the string I set?

The natural moment to set it is the day you open the account — the day-one account hardening guide treats it as part of that first session.

What an email looks like with and without the code

Say your code is Qm7_Rvr (an example only — don't reuse it). Line up a few emails that claim to be from Binance:

Where exactly the code sits in an email isn't spelled out — the help center only shows an illustration. The first time a genuine one arrives, note where it is; after that one glance is enough.

Which screen to use and what to type

The setting sits under Binance's security settings, alongside two-factor verification and login devices. The labels below follow Binance's help-center article, checked November 2026; menus move now and then, so go by what your app shows:

  1. In the app, "go to the menu icon, tap on your profile to launch the “Account Info” screen, then select [Security]." On the website: hover over the Profile icon → Account → Security, then scroll to Advanced Security.
  2. Tap [Anti-Phishing Code] - [Create] (on the website, click Enable next to it first).
  3. Type your code: 6 to 8 characters, three of the four types, no special characters. Not sure it'll pass? Check it against the examples in the next section.
  4. Submit, then: "Complete your verification with your 2FA or passkey". From then on genuine Binance emails and texts carry it.

Of all the security settings, this one is the quickest to finish and the easiest to forget you ever set. It stays silent until a fake email shows up.

Two Binance app screens: on the left the Security page with the "Anti-Phishing Code" row outlined in red below the 2FA list; on the right the Anti-Phishing Code intro page with a yellow Create button
In the app: Security → Anti-Phishing Code → Create · image from the Binance Help Center article What Is an Anti-Phishing Code and How to Set It up on Binance? (updated 2026-08-28) · collected 2026-11-08 · your app may look different · compiled from official material; this site is not Binance

Examples that pass and fail

The help center's three rules are length ("Be between 6 to 8 characters"), character mix ("Include at least three of the following character types: uppercase letters, lowercase letters, digits, and underscores") and "Code cannot contain any special character." Here are eight strings counted against them. The last column applies the 2022 blog rules, covered just below.

ExampleLengthTypes usedCurrent rules2022 rules
Qm7_Rvr7upper, lower, digit, underscore (4)ValidFails: under 8
abcd_1238lower, underscore, digit (3)ValidFails: no uppercase
Binance18upper, lower, digit (3)Valid, but guessablePasses
abc1236lower, digit (2)Invalid two typesFails
ABCD12348upper, digit (2)Invalid two typesPasses
Tg5#kp27upper, lower, digit, plus #Invalid # is a special characterFails
Ab3_4all 4Invalid too shortFails
Kx9_mR2pz9all 4Invalid over 8Passes

Note: rules from the English help-center article (updated 2026-08-28), checked 2026-11-14. Demonstration strings only — don't use them. Spaces and non-Latin characters aren't mentioned; with only four types listed, we infer they're rejected.

Rejected again? Count the characters, count the types, look for a stray symbol. Letters and digits alone are only two types. On an 8-character code, swap one digit for an underscore (ABCD1234 becomes ABCD_234); a shorter one can take an underscore on the end; an all-caps code needs one lowercase letter, an all-lowercase one needs a capital.

The rules you'll often find online are from 2022

Binance's 2022 blog post "Today’s Catch: Anti-Phishing Codes and How to Protect Yourself" (dated 2022-06-14) says: "The code must be a minimum of 8 characters, with both uppercase letters and numbers." The current help center says 6 to 8 characters, three of four types, no special characters — and recommends updating regularly without naming a frequency. When you set yours, follow the current rules.

Put side by side, they contradict each other in two places. ABCD1234, written to the old rule, fails today with only two types. Qm7_Rvr, valid under the current rules, is too short for the old one.

Valid isn't the same as hard to guess

Keep these apart. The help center lists format rules and says nothing about checking how guessable a code is. Binance1 meets every one of them, yet if anyone tried guessing, strings built around the platform's name are the obvious first tries (our judgement, not Binance's). The help center's own advice: "We recommend choosing a code that is not easily guessed but is easily recognized by you."

Beyond the format, avoid:

There are "anti-phishing code generator" pages around. Our advice is to skip them: whatever string a generator hands you, that web page has seen too. Building your own is easy — take a few letters from a random page of a book, mix the cases, drop in a digit and an underscore, stop at 6 to 8 characters.

Visible in your inbox doesn't mean shareableBinance's 2022 blog post is blunt about it: "The Anti-Phishing Code is highly sensitive personal information; under no circumstances should you share it with anyone, including Binance staff members." The help center adds: "If you suspect that your anti-phishing code has gotten leaked, make sure to update it as soon as possible." The logic, as we read it: a scammer who knows your code can put the right one in a fake email, and the check stops working.

Where it can't reach

The code only appears in the emails and SMS Binance sends you. Texts carry it but still need care of their own, and on the other channels below it never appears, so "is there a code" can't settle anything there:

To check a specific message, run the three steps in how to confirm a "Binance" message is genuine, and when you're unsure, go through the phishing-message authenticity self-check item by item.

How it shows across devices, and whether to rotate it

The code is tied to your account, not a device. Set it once, and whether you log in from the phone app, a desktop browser or anything else, Binance's emails and texts carry the same string. That's unlike an authenticator app, whose rotating codes are computed locally on one phone. New phone, new tablet, new laptop — none of it requires resetting the code.

On rotation, Binance's two sources differ, so here are both. The help center: "Like passwords, it’s a good practice to update your anti-phishing code regularly." No frequency given. The 2022 blog post: "Like passwords, it’s best to update your Anti-Phishing Code regularly — at least once per month." We won't set a schedule on Binance's behalf. These situations call for a change now:

Whatever you change it to has to be something you'll recognise on sight. A new code you promptly forget protects you less than an old one you know by heart.

Using it alongside your other defences

Each defence covers its own stretch:

The complete account-security checklist lays all of these out in order. The anti-phishing code is the "check the message" guard among them.

In one lineThe anti-phishing code defends against "being fooled by a fake email." It can't defend against market swings, and it's no substitute for keeping your own password and seed phrase safe. This piece is about account security only and isn't investment advice of any kind.

FAQ

Does the anti-phishing code appear in texts and phone calls?

In texts, yes; on calls, no. Binance's help center says the code is included in all genuine emails and SMS from Binance, so a text claiming to be Binance with no code, or the wrong one, may be phishing. It never appears on phone calls or in third-party messaging apps, so a caller or a DM claiming to be support has to be checked another way.

What format does the anti-phishing code need, and why does it keep saying invalid?

Binance's current help-center rules: 6 to 8 characters; at least three of uppercase letters, lowercase letters, digits and underscores; no special characters. A rejected code is usually one of three things: only two character types (abc123, ABCD1234), a length outside 6–8 (the 4-character Ab3_, the 9-character Kx9_mR2pz), or a symbol such as # @ ! slipped in. The help center doesn't mention spaces or non-Latin characters; since it lists only those four types, we infer they aren't accepted. Checked November 2026.

What makes a good anti-phishing code?

Passing the format check and being hard to guess are two separate things: the help center lists format rules only, not a guessability check. Binance1 is valid but obvious; something patternless that mixes all four types, like Qm7_Rvr, is far better. Avoid nicknames, birthdays, phone digits and handles, and never reuse a password.

Does setting an anti-phishing code mean I can't be phished?

No guarantee. It only helps you judge emails and texts that claim to come from Binance; it can't stop fake calls, fake support DMs, spoofed sites, or an infected device, and even a message with the right code is no reason to follow its links. Use it alongside two-factor verification, a withdrawal whitelist and the rest.

What if I forget the anti-phishing code I set?

Set a new one. In Security, open Anti-Phishing Code and choose Change Anti-Phishing Code, then confirm with your 2FA or a passkey. Binance's help article describes changing the code, not displaying the old one, so pick a replacement you'll recognise at a glance.

CM
Cheng Mo · Zhenku Editorial

"Cheng Mo" is a pen-name and doesn't represent any licensed expert. What we do is explain Binance's official security settings and public rules in an order an ordinary user can follow, checked line by line against Binance's own pages. We don't give investment advice; if you spot something we got wrong, please tell us via corrections.

Sources

  • Binance Help Center · What Is an Anti-Phishing Code and How to Set It up on Binance? (binance.com/en/support/faq, updated 2026-08-28, checked 2026-11-14)
  • Binance Blog · Today’s Catch: Anti-Phishing Codes and How to Protect Yourself (binance.com/en/blog, dated 2022-06-14, edited 2022-06-22, checked 2026-11-14)