Watch a firewall decide, message by message.
Five labelled sample messages go through the same checks an operator SMS firewall runs. Each gets a verdict, the reason, the inspection latency and the action taken. Switch to the twin view to see the same message from both sides: the enterprise's delivery outcome and the operator's firewall and revenue decision.
Sample traffic
Sample data- Sender
- INFO-DLVR
- To
- +971 55 ••• 1082
- Content
- Your parcel is on hold. Pay the 2.50 redelivery fee at parcel-fee[.]example/pay
Newly seen look-alike domain, a generic sender ID not registered to any brand, and a payment lure.
Dropped before delivery. The URL goes on the blocklist for every route.
Enterprise view
The impersonated brand's customers never receive the lure.
Operator view
Subscriber harm prevented; the incident is logged for the regulator report.
No revenue lost: this traffic was never billable.
Sample data: fictional senders, masked numbers and defanged links. Latencies are illustrative.
What the workbench shows
Verdict
Allow, block, throttle or reroute: the four outcomes an operator firewall applies.
Reason
The signals that decided it, stated in plain words so an analyst can audit the call.
Latency
Inspection time per message. Screening runs inline, so it has to stay in the low milliseconds.
Twin view
The same message from both sides: what the sending enterprise sees and what the operator decides and earns.
See it on your own traffic.
Our A2P revenue and fraud assessment reviews a sample of your network's traffic and shows where grey routes, pumping and spoofing are costing you revenue.
Questions about SMS firewall verdicts
What is the difference between smishing and SMS pumping?
Smishing targets the recipient: a fake message that lures them to a link or a phone number. SMS pumping targets the sender: fake sign-ups drive one-time-code messages to number ranges where someone earns from the traffic. A firewall blocks the first on content and sender signals and throttles the second on velocity and conversion.
Why does a firewall reroute some traffic instead of blocking it?
Grey-route traffic is often a genuine application message that entered on a cheaper person-to-person route. Moving it onto the A2P interconnect keeps the message flowing for the end user and restores the operator's termination revenue.
Is this real traffic?
No. Every message on this page is anonymised sample traffic with fictional senders, masked numbers and defanged links. The assessment runs the same analysis on your own traffic.