Anonymous ID: d05aff Aug. 6, 2020, 8:42 p.m. No.10207007   🗄️.is 🔗kun   >>7026

>>10206893

The problem with that is 11.5 and 11.3 aren't IP addresses. And I also don't see how they would relate to the 11.11.18.0/24 network block.

 

You could make an argument that they are all their own /16 network (11.3.0.0/16, 11.5.0.0/16) however I don't see how that applies in the big picture.

 

Of course, I could be wrong.

Anonymous ID: d05aff Aug. 6, 2020, 8:46 p.m. No.10207080   🗄️.is 🔗kun   >>7096 >>7106 >>7180

>>10207026

It's the same network. The 11.0.0.0/8 network belongs to the DoD. This includes 11.3 11.5 etc etc. Has nothing to do with physical location either.

 

NetRange: 11.0.0.0 - 11.255.255.255

CIDR: 11.0.0.0/8

NetName: DODIIS

NetHandle: NET-11-0-0-0-1

Parent: ()

NetType: Direct Allocation

OriginAS:

Organization: DoD Network Information Center (DNIC)

Anonymous ID: d05aff Aug. 6, 2020, 8:58 p.m. No.10207202   🗄️.is 🔗kun   >>7255

>>10207158

>I just did a tracert on 8kun.top and there are no 11.x.x.x servers

You wouldn't see 11.x.x.x servers, that is not publicly routed (not in the global BGP tables).

 

You COULD see it if you transit someone's network that configured their network with 11.x.x.x addresses because they assume that the DoD will never route the 11.0.0.0/8 block, or if they did they (or their customers) would never need to access them.

This is possible because of the way traceroute works.

 

>http://geoiplookup.net/ip/23.225.188.18

Looking into what you are saying with this.