Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
SMS authentication is a way of checking identity with a numeric code sent to a mobile phone. At login, a code is sent by short message (SMS) to the registered phone number, and the person who can type it in is treated as the genuine user.
How does SMS authentication work?
Think of sending a letter to the registered address and treating the person who can receive it as genuine. SMS authentication uses a phone number instead of an address. It also checks that you hold that phone, in addition to the password, so it is one form of multi-factor authentication.
The code that arrives is a one-time password that becomes invalid once used. It works with any mobile phone, without installing a dedicated app, so it takes little effort on the user's side.
NIST's guideline, SP 800-63B-4, places methods that send a verification value over the telephone network as a restricted authenticator, one whose use is limited. When it is used, the guideline also asks that users can choose another method that has no such restriction. It also sets out the risks particular to that route. Read about the damage from missing multi-factor authentication on its own vulnerability page. The free URL check cannot tell which services send codes by SMS, because that is not visible from outside.
Why does SMS authentication matter?
Even if the password leaks, login stops for someone who does not hold the phone that receives the code. Many users already carry a mobile phone, so it is an easy method to introduce as a first step.
On the other hand, NIST's guideline lists the weak points of this method. One example is deceiving the mobile carrier into moving a phone number to the attacker's device so that SMS can be intercepted (SIM swap). It also describes as a danger the case where a malicious app on the device reads the code that arrives.
A throwaway code also cannot keep up with a method that makes someone type it into a fake site and immediately types it into the real site to get in. There is a practical drawback as well: where there is no signal, the code cannot be received at all.
That does not mean you need to drop SMS authentication. It still makes defense firmer than a password alone. A passkey, which uses a key tied to a device, is the kind of method that resists fake sites.
Related terms
- One-time password: a throwaway password that becomes invalid once used
- SIM swap: a method that takes over a phone number to intercept an SMS code
- Smishing: a deceptive method that uses SMS to lead people to fake sites
- Passkey: a way to log in without a password, using a key tied to a device
Next step
For the services where you now receive codes by SMS, see which could move to an authenticator app or a passkey. Remember to review the registration when you change your phone number. The free URL check covers only the public side of your site. If you want help deciding what to use in place of SMS codes, ask in a free consultation.
Frequently asked questions
Should I stop using SMS authentication?
Not necessarily. It makes defense firmer than a password alone. NIST's guideline treats it as a restricted authenticator and asks that users can also choose a method without that restriction.
A code arrived by SMS but I did not do anything. What should I do?
Do not enter the code, and change the password for that service at once. Someone who knows the password may be trying to log in. Also check whether you reuse the same password elsewhere.
Frequently asked questions
Should I stop using SMS authentication?
Not necessarily. It makes defense firmer than a password alone. NIST's guideline treats it as a restricted authenticator and asks that users can also choose a method without that restriction.
A code arrived by SMS but I did not do anything. What should I do?
Do not enter the code, and change the password for that service at once. Someone who knows the password may be trying to log in. Also check whether you reuse the same password elsewhere.