I don’t think there is any tool/service that supports it.
There is no standard way of signing Segwit messages, so they just did their way (thus they are the only ones supporting it so far).
For segwit addresses there is no standard. You can sign and verify only using trezor-trezor device. Which make this feature a bit pointless.
The problem is that there is no standard algorithm for verifying with segwit addresses. In particular, the site you mentioned will never accept a signature for a 3.. or bc1.. address as valid. It doesn't matter what signature you use. I think the same is true for Bitcoin Core. You can't create any signature for a 3.. or bc1.. address that Bitcoin Core would accept.
To solve this, we need a standard algorithm for segwit addresses and we need everyone to accept it.
The algorithm the TREZOR wallet uses is a straight-forward extension of the existing signature schemes. It signs the message with the public key and only changes the first character of the signature to indicate that it is a segwit address. Previously, the first character was either "H" for old uncompressed keys, or "I" for compressed keys (introduced 2012). We added "J" for segwit p2sh addresses (3...) and "K" for bc1q... addresses.