• TimeSquirrel@kbin.melroy.org
    link
    fedilink
    arrow-up
    0
    ·
    7 hours ago

    I was nosy:

    traceroute to 104.244.42.129 (104.244.42.129), 30 hops max, 60 byte packets
    
     1  192.168.10.1 (192.168.10.1)  0.369 ms  0.494 ms  0.656 ms
    
     2  lo0-100.BLTMMD-VFTTP-340.verizon-gni.net (173.64.66.1)  3.065 ms  2.969 ms  3.652 ms
    
     3  100.41.25.140 (100.41.25.140)  6.005 ms  6.072 ms 100.41.25.138 (100.41.25.138)  5.985 ms
    
     4  0.ae15.GW10.IAD8.ALTER.NET (140.222.225.39)  10.372 ms  10.317 ms  11.678 ms
    
     5  WS-Twitter-Twitter.customer.alter.net (204.148.79.138)  11.323 ms  10.430 ms  10.470 ms
    
     6  * * *
    
     7  104.244.42.129 (104.244.42.129)  28.496 ms  34.967 ms  25.307 ms
    

    It’s kinda funny they still have the name “twitter” plastered all over their infrastructure.

    • CheezyWeezle@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      7 hours ago

      Pro tip; you should probably delete or censor this, it looks like you just essentially doxxed your computer. This traceroute shows your internal IP, the fact you have Verizon as an ISP and which edge server is hosting your connection, your external IP, etc.

      • Sinthesis@lemmy.today
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        6 hours ago

        shows your internal IP

        nearly everyone uses 192.168.1.1 for their local-non-enterprise network

        Verizon as an ISP

        You missed BLTMND = Baltimore Maryland, this is the only thing that is identifying but if Bmore is large metropolitan area so youve narrowed it down to ~million people

        edge server is hosting your connection

        shows their gateway not whatever you just said

        your external IP

        no it doesnt.

        /edit carriage returns