Hier is de traceroute naar telenet TRACEROUTE (using port 443/tcp) HOP RTT ADDRESS 1 0.00 ms 192.168.0.1 2 ... 4 5 22.00 ms dD5E0F956.access.telenet.be (21x.22x.24x.8x) 6 25.00 ms dD5E0F886.access.telenet.be (21x.22x.24x.13x) 7 22.00 ms web-apps-vip.prd.telenet-ops.be (19x.13x.13x.4x) Pinging telenet.be [19x.13x.13x.4x] with 32 bytes of data: Reply from 19x.13x.13x.4x: bytes=32 time=16ms TTL=58 Reply from 19x.13x.13x.4x: bytes=32 time=15ms TTL=58 Reply from 19x.13x.13x.4x: bytes=32 time=17ms TTL=58 Reply from 19x.13x.13x.4x: bytes=32 time=15ms TTL=58 Ping statistics for 19x.13x.13x.4x: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 17ms, Average = 15ms En ik heb geen idee hoe ik precies het ip van deze server vindt dus dit kan het foute ip-adres zijn maar hier is de traceroute naar wat ik denk dat het ip is van de server Starting Nmap 7.97 ( https://nmap.org ) at 2025-08-04 20:07 +0200 Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 7.62 seconds En als ik het probeer met -Pn TRACEROUTE (using proto 1/icmp) HOP RTT ADDRESS 1 2.00 ms 192.168.0.1 2 19.00 ms d8D872001.access.telenet.be (14x.13x.3x.1) 3 20.00 ms dD5E0CF22.access.telenet.be (21x.22x.20x.3x) 4 ... 5 6 21.00 ms 4.6x.7x.5x 7 21.00 ms ae1.3102.ear8.ams1.neo.colt.net (17x.7x.1x.5x) 8 ... 30 Nmap done: 1 IP address (1 host up) scanned in 212.32 seconds
... Meer weergeven