Wen wundert das noch?! Roblox ist schon seit vielen Jahren immer mit bei den Spitzenreitern, wenn es um illegale Account-Dumps geht!
Die verwendete Site → releasethen.site ist immer noch aktiv:
| Hostname | Type | TTL | Priority | Content |
|---|---|---|---|---|
| releasethen.site | SOA | 3600 | ns1.dns-parking.com dns@hostinger.com 2022112401 10000 2400 604800 600 | |
| releasethen.site | NS | 21600 | ns2.dns-parking.com | |
| releasethen.site | NS | 21600 | ns1.dns-parking.com | |
| releasethen.site | A | 1800 | 156.67.73.119 | |
| releasethen.site | AAAA | 1800 | 2a02:4780:b:677:0:1d4e:c476:1 | |
| releasethen.site | MX | 3600 | 10 | mx1.titan.email |
| releasethen.site | MX | 3600 | 20 | mx2.titan.email |
| www.releasethen.site | A | 1800 | 156.67.73.119 | |
| www.releasethen.site | AAAA | 1800 | 2a02:4780:b:677:0:1d4e:c476:1 | |
| www.releasethen.site | CNAME | 14400 | releasethen.site | |
| www.releasethen.site | MX | 3600 | 20 | mx2.titan.email |
| www.releasethen.site | MX | 3600 | 10 | mx1.titan.email |
PING releasethen.site (156.67.73.119) 56(84) bytes of data.
64 bytes from 156.67.73.119: icmp_seq=1 ttl=35 time=56.4 ms
64 bytes from 156.67.73.119: icmp_seq=2 ttl=35 time=56.4 ms
64 bytes from 156.67.73.119: icmp_seq=3 ttl=35 time=56.4 ms
64 bytes from 156.67.73.119: icmp_seq=4 ttl=35 time=56.4 ms
64 bytes from 156.67.73.119: icmp_seq=5 ttl=35 time=56.4 ms
— releasethen.site ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 56.445/56.473/56.490/0.260 ms
traceroute to releasethen.site (156.67.73.119), 30 hops max, 60 byte packets
1 ip-10-0-0-14.ec2.internal (10.0.0.14) 1.264 ms 1.249 ms 1.289 ms
2 216.182.231.116 (216.182.231.116) 17.358 ms 216.182.231.42 (216.182.231.42) 3.564 ms 216.182.238.155 (216.182.238.155) 4.891 ms
3 100.66.12.76 (100.66.12.76) 385.204 ms 100.66.12.88 (100.66.12.88) 13.442 ms 100.65.81.160 (100.65.81.160) 9.311 ms
4 100.66.40.252 (100.66.40.252) 2.453 ms 100.66.14.158 (100.66.14.158) 17.185 ms 100.66.38.222 (100.66.38.222) 17.699 ms
5 241.0.4.193 (241.0.4.193) 1.867 ms 100.66.43.144 (100.66.43.144) 19.973 ms 241.0.4.216 (241.0.4.216) 1.855 ms
6 241.0.4.207 (241.0.4.207) 1.862 ms 240.0.40.19 (240.0.40.19) 1.385 ms 241.0.4.198 (241.0.4.198) 1.464 ms
7 240.0.40.23 (240.0.40.23) 1.474 ms 240.0.40.28 (240.0.40.28) 1.461 ms 240.0.40.25 (240.0.40.25) 1.473 ms
8 242.0.170.129 (242.0.170.129) 1.433 ms 240.0.40.21 (240.0.40.21) 1.409 ms 242.0.171.17 (242.0.171.17) 1.669 ms
9 52.93.28.167 (52.93.28.167) 1.779 ms 52.93.28.191 (52.93.28.191) 1.901 ms 52.93.28.195 (52.93.28.195) 8.908 ms
10 52.93.28.183 (52.93.28.183) 2.475 ms 52.93.28.171 (52.93.28.171) 2.224 ms 52.93.28.169 (52.93.28.169) 11.303 ms
11 * * 100.100.2.22 (100.100.2.22) 2.079 ms
12 * * 4.69.207.161 (4.69.207.161) 56.886 ms
13 IRON-MOUNTA.bear2.Phoenix1.Level3.net (4.15.8.250) 57.079 ms IRON-MOUNTA.bear1.Phoenix1.Level3.net (4.15.8.34) 56.841 ms *
14 po291.cr02.ngspn.azp1.imdc.com (148.51.252.68) 57.106 ms 57.029 ms *
15 po31.cr02.ngspn.azp1.imdc.com (148.51.252.52) 57.189 ms po301.cr02.ngspn.azp2.imdc.com (148.51.252.70) 57.415 ms *
16 ae1.ter1.phx2.us.zip.zayo.com (64.125.29.231) 53.452 ms 53.574 ms po501.ar01.ngspn.azp1.imdc.com (148.51.252.203) 57.417 ms
17 156.67.75.247 (156.67.75.247) 57.825 ms 153.92.2.201 (153.92.2.201) 57.174 ms 156.67.75.247 (156.67.75.247) 57.751 ms
18 * po301.cr02.ngspn.azp1.imdc.com (148.51.252.130) 56.367 ms 56.467 ms
19 po501.ar01.ngspn.azp1.imdc.com (148.51.252.203) 56.004 ms * po301.cr02.ngspn.azp1.imdc.com (148.51.252.130) 56.683 ms
20 * * *
21 156.67.75.247 (156.67.75.247) 55.575 ms * *
22 156.67.75.247 (156.67.75.247) 55.421 ms * 55.617 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
searchblox.site gibt hingegen einen 502 Bad Gateway - Fehler aus!
Kinder lassen sich halt leichter täuschen. 
…sind aber auch viel schneller enttäuscht, als erwachsene Nutzer! 
