Set up a packet sniffer on your network and check it out if you like, traffic passing through Warp is encrypted.
Warp cannot guarantee that every packet passes through Warp, especially on a smartphone environment as there are a lot of underlying requirements (for example, VoLTE and MMS are both inherently data services, cannot be routed through a VPN). It is not uncommon for some requests to system services/features to not use a user-level VPN, this will include DNS in some cases.
Warp isn’t intended to address the situation where a client is actively trying to avoid the VPN, which is what happens when you use this type of tool.
Yes and yes. It’s not a problem. Even the official CF blog post linked to an alternative (TOR).
I’ve sampled quite a few free VPNs. Windscribe was the winner for me.
This actually worked, the real IP is not shown on DNS leak and not on IP leak. Neat!
Well I don’t see similar behavior as you see when Warp is enabled in my mobile device (android 9).
This is my dnsleak extended test with Warp enabled:
This is my dnsleak extended test with Warp disabled:
However it does not matter anymore to me anymore as I don’t see any use for Warp currently.
Like Cloudflare members pointed out there has been misunderstanding about Warp VPN so I have to look elsewhere unfortunately.
The tool that I tested—one of the two linked in the original post—wasn’t doing anything fancy to evade WARP. It was just sending basic requests and looking to see which resolvers were used. If that particular test fails, WARP isn’t active or isn’t working properly; it’s not encrypting the last mile.
Again, I was unable to reproduce this bug—the test succeeded. If it’s failing for you, try toggling WARP off and on again.