I used to have one like this, it was 1 and my nickname, and it was a great thing,
-snip- I suggest not using it because the private keys will be with them,
This sounds like a "
Vanity Address" which has a number of bruteforce-able prefix limited by your machine's specs.
On the other hand, the address in the OP is known as a "
Burn Address" generated by selecting valid base58 characters and computing the correct checksum to be valid.
Unlike vanity address, it's not produced by bruteforcing address with prefix starting from a private key.
-snip- I have never seen any segwit versions of this, some say that it is possible and there are some examples I have seen but it's so few and rare that I think it could just be coincidence as well so I am not really sure if segwit has this yet.
Both vanity and burn address has SegWit variant.
For vanity address, the process is similar; start fron a private key anf check if the address matched the desired prefix.
Repeat if not (
bruteforce).
Use VanitySeach if you want to create one yourself.
For burn address, the characters to select are from bech32 instead of base58. Then, it's the same, compute the checksum (
for bech32 address) to produce a valid SegWit address.
Now, examples of this is rare since there's no use-case for such burn address aside from "
Proof-of-Burn" and the useless spam transaction example in the OP.