{"id":1012,"date":"2026-06-04T09:00:00","date_gmt":"2026-06-04T02:00:00","guid":{"rendered":"https:\/\/phoneparental.com\/blog\/star-21-code-explained\/"},"modified":"2026-06-24T14:29:58","modified_gmt":"2026-06-24T07:29:58","slug":"star-21-code-explained","status":"publish","type":"post","link":"https:\/\/thetruthspy.com\/blog\/star-21-code-explained\/","title":{"rendered":"*#21# Explained: Does It Really Show If Your Phone Is Tapped?"},"content":{"rendered":"

\u2018Dial *#21# \u2014 if it shows anything, your phone is tapped!\u2019 The viral claim is everywhere, and it badly overstates what this code does. Below you will find exactly what *#21# checks, how to read the result honestly, and why it is not a spyware detector \u2014 in plain language, with the practical steps that actually matter.<\/p>\n

The aim is to leave you confident rather than anxious, so we will be clear about what genuinely matters and what is simply background noise not worth worrying about.<\/p>\n

What *#21# checks<\/h2>\n

It queries your carrier for unconditional call, SMS and data forwarding \u2014 settings that send your incoming calls or texts to another number automatically, every time.<\/p>\n

\"*#21#
*#21# Explained \u2014 what to check<\/figcaption><\/figure>\n

How to read the result<\/h2>\n

A normal result shows forwarding disabled or \u2018not forwarded\u2019. If it shows your calls or texts being forwarded to a number you do not recognise, that is worth cancelling with ##002# and investigating with your carrier.<\/p>\n

Why it is not proof of tapping<\/h2>\n

Forwarding is a legitimate phone feature \u2014 voicemail uses it. Seeing forwarding status does not reveal spyware, microphone access, or location tracking, none of which run through the carrier\u2019s forwarding system.<\/p>\n

\"*#21#
*#21# Explained \u2014 a closer look<\/figcaption><\/figure>\n

Other forwarding codes worth knowing<\/h2>\n

Beyond *#21#, a small family of related codes rounds out the picture. *#62# shows where calls go when your phone is unreachable, *#67# shows diversion when you are busy, and ##002# clears every forwarding rule at once.<\/p>\n

If you ever find forwarding you did not set, clearing it and changing your carrier-account password together close the loop, since forwarding can be re-applied by anyone who controls that account.<\/p>\n

When *#21# is genuinely useful<\/h2>\n

If a stranger had access to your account or device, they could in theory set up call forwarding to intercept verification codes. That is a real, narrow risk, and *#21# is a quick way to check for it.<\/p>\n

If you find unexpected forwarding, cancel it, change your carrier account password, and contact the carrier to confirm no other changes were made.<\/p>\n

What to check beyond the code<\/h2>\n

For the broader question of tracking, audit app permissions, accessibility settings and your signed-in account devices \u2014 the places monitoring actually lives.<\/p>\n

What matters most here<\/h2>\n

It is worth seeing how these pieces fit together. What *#21# checks is usually where to look first; why it is not proof of tapping and other forwarding codes worth knowing matter most when something there already seems off.<\/p>\n

The picture only resolves when signs agree. Take a cluster seriously and follow through; treat a single outlier as the ordinary thing it almost always turns out to be.<\/p>\n

It helps to approach this the way you would any small household task: methodically, without drama, and with the expectation that the result is far more likely to be reassuring than alarming once you actually look.<\/p>\n

It also helps to set a realistic bar for action. Not every imperfection needs fixing, and a phone that is a little slower or warmer than you would like is usually just an older phone, not a compromised one \u2014 context that keeps your response proportionate.<\/p>\n

Keep in mind that the steps here are equally useful as a routine, not just a response to worry. Running through them occasionally, when nothing is wrong, keeps your phone in good shape and makes any genuine change much easier to spot when it does occur.<\/p>\n

The routine in full<\/h2>\n

Here is the whole thing as one short sequence \u2014 each step is quick, and together they take just a few minutes:<\/p>\n

    \n
  1. Dial *#21# and read the forwarding status.<\/li>\n
  2. If forwarding is on to an unknown number, dial ##002# to cancel it.<\/li>\n
  3. Change your carrier account password.<\/li>\n
  4. Audit app permissions and accounts for actual monitoring.<\/li>\n<\/ol>\n

    Reading the signs without alarm<\/h2>\n

    The claim that *#21# detects phone tapping is false. It only reveals call-forwarding settings \u2014 useful, but not a spyware test.<\/p>\n

    Stay with that framing and you will spend your energy on the things that matter rather than the things that merely look alarming.<\/p>\n

    In short<\/h2>\n

    Treat *#21# as a quick call-forwarding check, not a verdict on whether your phone is monitored.<\/p>\n

    Where covert monitoring erodes trust, TheTruthSpy<\/a> is built to be transparent \u2014 visible on the device and set up with the person who uses it. It is quick to get started \u2014 and the features are there if you want to look before you do. It keeps things simple and honest: one visible app, agreed by everyone it touches.<\/p>\n

    Quick answers<\/h2>\n

    If *#21# shows forwarding, is my phone hacked?<\/h3>\n

    Not necessarily. Some forwarding is normal (voicemail). Unexpected forwarding to an unknown number is worth cancelling and reporting to your carrier, but it is not by itself proof of spyware.<\/p>\n

    How do I turn off forwarding I didn’t set?<\/h3>\n

    Dial ##002# to cancel all call forwarding, then change your carrier account password to stop it being re-enabled.<\/p>\n

    Are these codes different on every network?<\/h3>\n

    The core forwarding codes are broadly standard on GSM networks, but a few carriers customise them. If a code does nothing, check your carrier’s help pages for their equivalent.<\/p>\n