How about we all worry about our own legalities and not assume or infer that others are breaking the laws when there is no indication that this was done. Thanks to Alice for making a logical explanation for the others who seem to need to exert some authoritative response.
This is hard to explain as I am still trying to figure out how the address translation is working. I didn't do anything illegal in scanning anything, it is all just looking at the port 80 on a web server, scanning the IP addresses requesting the information.
I'm not sure how the static IP addresses work behind an ISP NAT router vs dynamic IP addresses, but it seems that the static routes use the account holders name as the translated IP address. It's like a local DNS for behind the ISP's router. Just like you name computers on your network, you can access your computer by either the IP address or the computer name. With this ISP, for some reason, when a web page is requested it uses the "account name" instead of the IP address.
example: Computer Name = desktop; IP address 192.168.1.101
\\desktop\C$ = \\192.168.1.101\C$
You can use either of the above to do the same function if the local DNS/DHCP server is working (I think that is the server that translates the IP to the computer name).
So, what I have found on this ISP is that when a web page is requested, the address is represented as the "account name" instead of the IP address.
Example: Static IP address= 272.123.34.242; "Modem name" = ltn-AccountHoldersName.branch.ISPname.net (ltn-JohnDoe.branch.ITTinternet.net)
Therefore 272.123.34.242=ltn-AccountHoldersName.branch.ISPname.net when entered into the browser.
So, if you want to access your network/modem you can use the IP address or the "Modem name" to get to the address. This is just like accessing a domain name vs the IP address of any website.
I was scanning the incoming traffic of a webserver, looking at IP addresses, and found that some were coming through as non-numeric numbers, like the example I gave you. A search resulted over 7,000 other results of static IP's with account holders names as the translated "ISP domain name".
I don't know what to call the "ltn-AccountHoldersName.branch.ISPname.net " - which results in the same as entering the static IP address of the account holder.
I just don't know why the ISP is using the "account name" instead of the IP address outside their network and how that is working in getting traffic back to the requester.
Does that make any sense now?
Also, if the Static IP address is in any way related to a sub-sub-sub domain name with the account holders name in it, then I think that is a breach in security on the ISP side as well as a number of other problems that I see. There should be a UID instead of the account holders name. Never should the account holders name be used in any public or private domain name unless specifically desired by the user.