Hide Phone Numbers in US Networks (*67 Spoofing)
Dial *67 immediately before the US number to request caller-ID blocking for that call, if your carrier supports it. This hides your number from the recipient’s ordinary caller-ID display; it does not change your number or make the call anonymous. Carriers and certain services may still receive identifying information, and emergency or toll-free calls are exceptions.
If you want to make a private call, the key is to distinguish caller-ID blocking from spoofing. I treat *67 as a display setting for one call, not a way to erase or replace the number behind it. That difference helps set realistic expectations and prevents accidental reliance on a feature that cannot provide full anonymity.
What *67 Does and Does Not Do
*67 is a per-call caller-ID blocking prefix. Where a provider supports it, the code asks the network to withhold your number from the ordinary caller-ID display on that call. It does not change your number, remove it from network records, or guarantee that every recipient will see “Private.”
In everyday use, people sometimes call this “spoofing.” That term is inaccurate here. Caller-ID spoofing means presenting a different number; *67 requests that your own number not be displayed to the recipient. The distinction matters because a blocked display is not the same as an untraceable call.
The federal caller-ID framework includes 47 CFR § 64.1601, which addresses caller-ID services, blocking, and exceptions. The way a blocking request works in practice also depends on carrier implementation, the type of line, and the destination. So, treat *67 as a limited privacy measure, not a universal rule.
Your originating carrier still handles the call and can associate it with your service. Some downstream systems may also receive identifying information for routing, security, billing, or service purposes. The person answering may see a label such as “Private,” “Blocked,” or “No Caller ID,” but labels can vary by device and provider.
Confirm Carrier Support and Call Type
Carrier support is the first check because *67 behavior can vary across mobile, landline, and VoIP services. Before relying on it, confirm that your provider supports per-call blocking on your specific line and learn how it handles the kind of number you plan to call.
Check your provider’s support page or contact customer service. Ask specifically whether *67 blocks caller ID for an outgoing call on your line, whether any setup is needed, and whether the feature works for domestic calls to the destination you have in mind. Do not assume a code works the same way on every service.
Also consider the recipient’s settings. A person or business can reject calls marked private or unknown. If the call does not connect, the recipient’s system may be blocking withheld caller ID rather than indicating a problem with your number or the prefix.
Before you dial, classify the call:
- Ordinary personal or business number: Per-call blocking may work if both the carrier and destination support it.
- 911: Do not rely on caller-ID blocking. Emergency calls may provide identifying or location information to support response.
- Toll-free number: Blocking may not prevent identifying information from reaching the service. Toll-free numbers include 800, 888, 877, 866, 855, 844, and 833.
- Special-purpose service: A network or service provider may receive information needed to handle the call.
The practical next step is to verify support before using the code for a call where the display outcome matters.
Place a Per-Call *67 Call
Per-call means you enter the prefix separately for each call you want to make with caller-ID blocking. It is not a setting that should be assumed to carry over to the next call. Use the normal dialing format your carrier requires, with *67 immediately before the destination number.
For a US 10-digit number, enter:
*67 + area code + seven-digit number
For example, if the destination is 212-555-0146, dial *672125550146. Do not add spaces when entering it on a keypad. If your provider requires a leading 1 or uses a different dialing format, follow that provider’s instructions.
Use this sequence:
- Confirm the destination is an ordinary number, not 911 or a toll-free line.
- Check that your carrier supports *67 on your line.
- Enter *67 immediately before the destination number.
- Place the call and ask the recipient what appears on caller ID, if appropriate.
- Enter the prefix again before any later call where you want blocking.
If you usually use a contact list or a phone’s redial function, make sure the prefix is included for that individual call. A call made later from the contact entry may not include *67. Do not assume that a previous blocked call means the next one is also blocked.
Verify the Recipient Display
A test call is the most direct way to check what the recipient sees. A successful connection alone does not confirm that the number was hidden; ask the recipient to check the caller-ID display while the call is active or immediately afterward.
Use a person who agrees to help, or another appropriate test destination. Tell them you are checking the display and ask for the exact wording shown. Depending on the phone and service, it may read “Private,” “Blocked,” “Unknown,” or another label. The words are not standardized across all devices.
| Test result | What it may indicate | Next step |
|---|---|---|
| “Private” or “Blocked” appears | The recipient’s display did not show your number in the usual way | Confirm the code was entered before the number |
| Your number appears | The request may not be supported or may not apply to that call | Ask your carrier about your line and destination |
| The call is rejected | The recipient may block private or unknown calls | Use an appropriate contact method that identifies you |
| No clear caller-ID result | The device or service may not show a usable label | Check with the recipient and carrier |
If your number appears, repeat the check only after confirming you dialed the right format. Then contact your carrier rather than trying unverified codes or apps. Blocking may be unavailable for that line, or the destination may handle the call differently.
Limits, Exceptions, and Privacy Risks
Caller-ID blocking changes what may be presented to the person receiving an ordinary call. It does not prevent the carrier from processing the call with the information needed to provide service, nor does it promise that all systems involved will lack identifying details.
Do not rely on *67 to conceal your identity from emergency services, your carrier, or network systems. Calls to 911 are treated differently from ordinary calls. Toll-free services may receive identifying information even when caller-ID display is blocked. Other special-purpose services may also handle caller information under different rules.
There is a second limit: the recipient controls whether to accept a call marked private or unknown. A phone, business phone system, or call-screening service may reject it. If the call is important, withholding caller ID can make it harder for the recipient to decide whether to answer or call back.
For privacy-sensitive situations, ask your carrier what information is retained and how its service works. Avoid sharing sensitive details in a call simply because you used *67. A blocked display is a modest privacy measure, not a shield against records, investigation, or network-level identification.
Practical Scenarios and Troubleshooting
These examples show how to apply the steps without treating caller-ID blocking as anonymity. They are common use cases, not claims about a particular carrier or phone. The best test is still a call made with the recipient’s consent and a check of the actual display.
Scenario 1: Calling a personal contact. You want to keep your number off the recipient’s ordinary display for one call. Confirm support, dial *67 followed by the number, then ask the person what appeared. If they see your number, stop and check with your provider.
Scenario 2: Calling a business with call screening. You use the prefix, but the call does not ring through. The business may reject calls labeled private or unknown. The code cannot force the call to connect; use a contact method that the business accepts.
Scenario 3: Calling a toll-free support line. You want to withhold your number, but the service may still receive identifying information or handle the call under different rules. Do not assume *67 will hide it from the service.
Troubleshoot in this order:
- Check that *67 comes immediately before the destination number.
- Confirm the dialing format with your provider, including whether a leading 1 is required.
- Verify the recipient’s display rather than judging only by whether the call connected.
- Ask the carrier whether per-call blocking is enabled and supported for that line.
- Do not use blocking to bypass a recipient’s screening choices or network controls.
Quick Reference
Use this reference to decide whether the feature fits the call. The key question is not only whether the code works, but also who may still receive identifying information and whether the recipient will accept a private call.
| Question | Practical answer |
|---|---|
| What do I dial? | *67, then the destination number in your carrier’s format |
| How often do I enter it? | Before each call you want blocked |
| Does it replace my number? | No. It requests caller-ID display blocking |
| Does it make me anonymous? | No. Carriers and some systems may still identify the call |
| Does it work for every destination? | No. Carrier, line type, destination, and recipient settings matter |
| What if my number still appears? | Confirm the format, then ask your carrier about support |
The safest takeaway is simple: verify the feature on your own line, test the display, and assume the call may still be identifiable to the carrier or certain services.
Frequently Asked Questions
Does *67 hide my number on every US call?
No. Availability and behavior vary by carrier, line type, destination, and recipient settings. Confirm support with your provider and test the display.
Is *67 the same as spoofing?
No. *67 requests that your number be withheld from ordinary caller ID. It does not replace your number with a different one.
How do I use *67 on a 10-digit US number?
Dial *67 immediately followed by the area code and seven-digit number. Follow your carrier’s instructions if it requires a different format.
Do I need to enter *67 before every call?
Yes. It is intended for per-call blocking. Do not assume it applies to later calls made from a contact or redial list.
Can the person I call still find out my number?
The recipient may not see it on ordinary caller ID, but the carrier and some network systems may still receive identifying information. The code does not guarantee anonymity.
Does *67 work when calling 911?
Do not rely on it to hide your identity from emergency services. Emergency calls may provide identifying or location information to support response.
Can I block my number when calling an 800 number?
Caller-ID blocking is generally unavailable for toll-free calls in the way it works for ordinary calls. The service may receive identifying information.
Why does a call marked private fail to connect?
The recipient may reject calls labeled private, blocked, or unknown. That is a recipient setting, not proof that the prefix was entered incorrectly.
What should I do if my number still appears?
Check that you entered *67 before the full destination number, then ask your carrier whether the feature works on your line and for that destination.
Does the FCC rule guarantee that *67 works with my provider?
No. 47 CFR § 64.1601 addresses caller-ID services, blocking, and exceptions, but actual availability and behavior depend on carrier implementation and the call type.
(This article was written by one of our staff writers, Richard Montclair. Visit our Meet the Team page.)
