![]() STIR/SHAKEN, doesn't mean there aren't people out there breaking the law. Also, just because the FCC has passed laws requiring the use of Until a full solution to validate caller identity on non-VoIP systems, there will still be spoofed calls. Non-VoIP systems, but as far as I know the details of the protocol haven't been finalized yet. That digital certificate is specific to STIR and only works in VOIP systems. You are referring to the STIR/SHAKEN protocols that the FCC requires all carriers in the United States to use as of June 30, 2021. Spoofed phone numbers are now being blamed on the carrier by the federal government in the US and they are being required to "certify" the phone number using a certificate from the carrier who "owns" the number, so soon this really shouldn't happen anymore. You could call your phone provider and ask them what the time frame is for hem to get in compliance. It actually doesn't sound like it would be to hard to implement, though I suppose the problem arises when you need carriers cooperating and sharing that information.doubt THAT will ever happen.Ī new law was made recently that sms and cellular carriers have to validate the number via an ownership certificate. What you suggesting is "message signing" (think SMB Signing), all they would have to do is verify that the IMEI matches the cell number before allowing the message to be processed. Having worked for a major US carrier, they of course know what IMEI matches what number as that is how you get access to the network to make calls and send texts. After all, we will be talking about a global architecture change, so even if the had it built and started implementing it, You could still get spam texts for probably a good 5 - 10 years. I'm sure they'd have to reengineer the SMS for one technical reason or another to make this work, but I'm too lazy to research it for them. So, sure you can put whatever you want in the caller ID section of the packet, but the carrier is going to put your real number in afterwards. I would hope the carrier knows what number goes with which IMEI number. ![]() Only forward incoming texts from "known " IMEI numbers on your network, then have "trusted" routes between the carriers. Y'know, it seems it would be a trivial fix - If you had the carrier be the one producing the phone number to the text message. In this day in age I expect that a proper solution is achievable. This would add accountability to the caller and the carrier. If a call cannot be traced to the caller it should be blocked unless the caller is on a list that follows regulated rules and even then some sort of unique identifier that masks the number but could still be correlated if lawfully needed. Trying to solve an issue with an App is a bandage approach and really doesn't get to the root of the issue. That needs all carriers and mobile phone platforms to set that standard which no one sees happening soon. These have been the best way I've seen to stop them until RCS finally gets fully integrated. They're now rolling out SPAM blocking apps with newer phones. It needed a law change which apparently has happened. First, it's only recent that carriers were even allowed to help with this since SPAM text and calls weren't illegal. Does anyone have a fresh idea?Ĭarriers are rolling out a few ways to get a hold of it. I wish there was Mimecast for text messages.Īside from changing my phone number, I'm out of ideas. I've looked for spam-text blocking apps, but I can't find anything. ![]() I use my DND schedule to limit some of the noise. When anyone does respond to an abuse claim, they claim that they thoroughly investigated and found nothing wrong. Verizon sold me on their Call Filter, and I have it but it doesn't work on these. I've complained to the domain name registrar (), to ICANN, to the FTC, to Cloudflare, and to Verizon (7726). The URL is also encoded with my phone number, so merely opening it tells somebody it's me. Each message contains a link to a unique domain name that is the combination of two random words, and the URL forwards to another random URL for a variety of fraud shops. The domain names are almost all being proxied by Cloudflare, so it is not possible to identify the web-hosting provider. I also cannot limit my incoming messages to who is on my contact list, because some MFA notifications also come from random numbers, and I do business with people not in my contacts (like any normal person). Since the phone numbers are unique every time, I can't block the messages that way (but I blocklist the numbers regardless). ![]() It happens every day, several times, and at all hours. For the past few weeks, I've been receiving spam texts from random spoofed numbers with messages that include a link to random URLs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |