"Incorrect search type" and bech32 addresses

[theborakompanioni]

Hey there!
First of all - thank you for your work. I am looking for something to protect ordinary humans when using btc for the first time
and therefore very much appreciate any effort in helping this clientele.
I stumbled upon a few things I'd like to understand better.

"Incorrect search type"

The very first example request on the api page returns an "incorrect search type" message.
https://api.cryptoscamdb.org/v1/check/0x25a51b3a7163352d4f32d0ed4a012b73fc32c08a

{
  "input": "0x25a51b3a7163352d4f32d0ed4a012b73fc32c08a",
  "success": false,
  "message": "Incorrect search type (must be a BTC/BCH/ETC/ETC/LTC address / ip address / URL)"
}

A p2pkh BTC-address starting with "1" works fine when it is in the blacklist. Otherwise the response is also, e.g.:

https://api.cryptoscamdb.org/v1/check/1PaLmmeoe5Ktv613UGBCxCUZ27owv9Q6XY

{
  "input": "1PaLmmeoe5Ktv613UGBCxCUZ27owv9Q6XY",
  "success": false,
  "message": "Incorrect search type (must be a BTC/BCH/ETC/ETC/LTC address / ip address / URL)"
}

Is this something you're aware of and working on, or is this expected behaviour?

On a side note:
If I specify the "coin" parameter it will return an "We do not support the queried coin yet."-error (as expected, since the feature is not yet supported):

https://api.cryptoscamdb.org/v1/check/1PaLmmeoe5Ktv613UGBCxCUZ27owv9Q6XY?coin=btc

{
  "success": false,
  "input": "1PaLmmeoe5Ktv613UGBCxCUZ27owv9Q6XY",
  "message": "We do not support the queried coin yet.",
  "coin": "BTC"
}

bech32

It also appears to having trouble with bech32 addresses.
e.g. "bc1q580e7qhrzt7gpfmmcm0etdedacnjdt22eh4s93" is a bech32 address in the blacklist - the "check" endpoint returns "type" as "ip".

https://api.cryptoscamdb.org/v1/check/bc1q580e7qhrzt7gpfmmcm0etdedacnjdt22eh4s93

{
  "input": "bc1q580e7qhrzt7gpfmmcm0etdedacnjdt22eh4s93",
  "success": true,
  "result": {
    "status": "neutral",
    "type": "ip",
    "entries": []
  }
}

It returns this message for all bech32 addresses, regardless whether they are contained in the blacklist.
Is there any plans to support bech32 addresses via the api in the future?

Thanks for your time and efforts.