I found a weird IP address on my network that had transmitted an insanely small amount of data. I put the address in my browser and got this. what the heck am I looking at?
UPDATE 10/4 6:47 EDT
I have been going through all the comments. THANKS!!!!!!
I did not know about the techniques listed, so they are extremely helpful.
Sorry for the slow update. As I mentioned below, I got behind with this yesterday so work cut into my evening.
I ran a port scan. The first syntax, -p, brought no joy. The nmap software itself suggested changing to -Pn. That brought an interesting response:
Failed to resolve "1-9999".
Nmap scan report for <Local IP Address>
Host is up (0.070s latency).
All 1000 scanned ports on 192.168.0.46 are in ignored states.
Not shown: 990 filtered tcp ports (no-response), 10 filtered tcp ports (host-unreach)
Nmap done: 1 IP address (1 host up) scanned in 6.03 seconds
Just to be absolutely sure, I turned off my work computer (the only windows box on my network) and reran the same syntax with the same results.
As I read this, there is definitely something on my network running windows that is not showing up on the DHCP.
UPDATE 10/6
I am working through all these suggestions. I am sorry for the slow responses, but I have my hands full with family weekend. I will post more next tomorrow.
But I did do one thing that has me scratching my head and wondering if this may be a wild goose chase.
I ran the nmap again per below with a completely fictional IP address within my normal range. It gave the exact same results:
nmap -A -T4 -p- -Pn <Fictional IP>
Starting Nmap 7.93 ( https://nmap.org ) at 2024-10-05 13:36 BST
Nmap scan report for <Fictional IP>
Host is up (0.054s latency).
All 65535 scanned ports on <Fictional IP> are in ignored states.
So, as others have saId this is just an unconfigured IIS server, which implies it's either a windows machine, or a windows based VM, well or someone put the default IIS files on another server, but that's unlikely.
When you say "weird" IP I'd wonder what you mean by that.
I think since it's probably a windows machine, from another windows machine typing nbtstat -A <ip> should give you the computer name and workgroup or domain they belong to. See if it matches anything you expect on your network.
If not, maybe it's time to change your WPA wifi key.
If you can, power stuff off and check if that web page is still available. Start with any Windows machines. It could be a virtual machine running inside of something else though.
does your router give you the MAC address of the device? You can look it up to see who manufactured it and then narrow down. This could be a device that has a web service running is all you are seeing right now.
Windows IIS probably from around the time of windows 8 so maybe 2012. Probably running on either windows server 2012 (like exchange, an active directory domain controller, or if you are unlucky sharepoint) or some weirdly configured appliance running windows 8 ish enterprise.
There was an appliance where the wifi chip was at the end of the power cable, embedded inside the plug. From the outside, you couldn't really tell. It was there so radiation inside the box couldn't affect the wireless signal as much.
I can imagine some genius thinking it's a good idea to run a server from inside a cable or a connected home appliance.
Get the MAC address from the ARP table, and look up the OIN, should help you determine if it's virtual or physical, and if physical the type of NIC it's using.
Depending on your router, it could have a docker setup with Windows on it. I've seen some strange shit on cheap routers with far too much processing power and storage.
Fun story, I live in a townhome, I had so bizarre network issues going on. Not able to stream to TV etc. finally started unplugging shit. Unplugged the router and saw the computer still happily downloading something WTF! Turns out a neighbor also had Ethernet over power and devices were randomly connecting to their network. Crazy ass shit.
Besides the MAC lookup suggestion, have you tried to simply find hostname in local DNS by reverse IP lookup, maybe that would shed some light.
Not sure if there is anything useful, but in browser just check site source, maybe there is something useful there that could help with identification. Does site have certificate? Do the standard browser network trace via dev tools F12, maybe something useful appears there.
And have you checked your router to see if this connection is connected to your Wi-Fi AP or Ethernet to narrow things down? If it is not possible to determine this from router, simply connect your main PC to Ethernet, disable AP in router settings and check if IIS site is still up. If it is not, enable AP again, does it come back early or it takes some time?
Lastly, if it still is a mystery, start powering off devices one by one to find the source. Based on comments it seems you have multiple devices, but I assume it would not take that long?
nmap's seeing the 1-9999 as the next argument (expecting an IP address). In -Pn, the n is a placeholder for the port numbers you want to scan, so you want -P1-9999