Topic: [SERVICE TEST] DTMF.IO (Read 170 times)

I do not know, of course. If you need certainty, you need to go a normal physical SIM route and pay monthly for a plan, of course. In any way, we all need to assume that all those bitcoin-paid services may disappear at any time.

Do you happen to know whether these numbers are unique? Or do they just wipe the history of the text messages and give it to somebody else whenever you stop paying for your subscriptions?

Guys,

I just started testing DTMF.IO and will report my results into this thread because it looks like an interesting service.

NOTE:
I do not have any association with DTMF.IO and do not receive any payments or other endorsements from them.

Test Results:

* I purchased two numbers (UK - Virtual Mobile, 3 euro/30 days, Canada - Virtual Landline, 3 euro/30 days). There are a lot of crypto payment options (even BTC Lightning!)
* I selected those numbers because they don't need any documents to be leased and, as per DTMF.IO, have "a history of successful SMS verification". Some numbers (especially, from Europe) require you to provide documents to lease the numbers.
* Although both numbers worked for my SMS verification needs, DTMF.IO explicitly states "Virtual numbers are not guaranteed to receive verification SMS messages (e.g. from online services)".
* Each number can be auto- or manually renewed. So, they are NOT disposable one-time numbers.
* I successfully received SMS messages into DTMF.IO web interface for each number: both SMS verification and SMS from my own mobile phone.
* I successfully forwarded incoming SMS messages to my email box (both SMS verification and from my mobile phone)
* I successfully forwarded all incoming call to my own mobile phone
* I successfully did an outgoing calls from the DTMF.IO web interface to my own mobile phone. The DTMF.IO phone numbers were displayed on my mobile phone as the calling parties.


If you want to know if it's possible to use those numbers for verification of a particular service, please feel free to ask here in the thread.