I agree with you that this type of access via IP and HTTP can be insecure.
However, in complex deployments (for example, 3 WAN connections with 3 static public IPs), we need the ability to access the device through any of those connections.
Using Keenetic KeenDNS works well in environments with a limited number of installed routers.
But how does KeenDNS handle a scenario with 3 WANs and 3 public IPs? FQDN associated to on of 3 IPs...
The requirement is to have selective access and full control of the device depending on the active WAN or reachable public IP.
In addition, for each router it is necessary to generate a dedicated KeenDNS FQDN and maintain a complete inventory.
Now imagine managing 100 routers, each with 2 or 3 public IP addresses.
My interest is to access the GUI directly via IP address, preferably using HTTPS.
Now via HTTP and IP work fine.