Russian
Search for "Korea Telecom"
| IP Pool | Country | State / Region | City | Coordinates | Timezone |
|---|---|---|---|---|---|
| 222.106.103.128 - 222.106.103.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.104.0 - 222.106.104.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.104.128 - 222.106.104.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.104.192 - 222.106.105.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.106.0 - 222.106.107.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.108.0 - 222.106.110.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.110.33 - 222.106.110.33 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.110.67 - 222.106.110.67 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.0 - 222.106.111.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.7 - 222.106.111.7 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.18 - 222.106.111.18 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.59 - 222.106.111.59 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.121 - 222.106.111.121 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.156 - 222.106.111.156 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.250 - 222.106.111.250 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.111.255 - 222.106.114.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.115.0 - 222.106.115.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.0 - 222.106.116.15 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.24 - 222.106.116.31 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.40 - 222.106.116.47 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.56 - 222.106.116.71 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.88 - 222.106.116.143 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.152 - 222.106.116.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.200 - 222.106.116.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.116.240 - 222.106.117.79 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.117.96 - 222.106.117.111 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.117.128 - 222.106.117.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.117.208 - 222.106.118.207 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.118.224 - 222.106.119.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.119.128 - 222.106.119.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.119.192 - 222.106.119.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.119.224 - 222.106.119.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.120.128 - 222.106.120.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.121.112 - 222.106.121.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.124.0 - 222.106.124.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.124.128 - 222.106.124.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.124.192 - 222.106.124.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.125.64 - 222.106.125.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.126.64 - 222.106.126.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.126.128 - 222.106.126.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.128.0 - 222.106.131.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.132.0 - 222.106.132.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.134.0 - 222.106.135.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.136.128 - 222.106.136.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.137.128 - 222.106.137.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.139.0 - 222.106.140.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.141.128 - 222.106.141.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.142.0 - 222.106.142.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.143.0 - 222.106.143.31 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.143.48 - 222.106.143.111 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.143.128 - 222.106.143.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.144.128 - 222.106.145.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.145.192 - 222.106.145.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.148.0 - 222.106.148.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.148.128 - 222.106.148.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.149.0 - 222.106.149.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.149.64 - 222.106.149.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.150.128 - 222.106.150.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.151.128 - 222.106.151.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.153.0 - 222.106.153.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.154.32 - 222.106.154.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.155.64 - 222.106.155.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.155.192 - 222.106.160.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.3 - 222.106.160.3 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.28 - 222.106.160.28 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.35 - 222.106.160.35 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.37 - 222.106.160.37 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.44 - 222.106.160.44 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.48 - 222.106.160.48 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.63 - 222.106.160.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.64 - 222.106.160.64 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.69 - 222.106.160.69 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.84 - 222.106.160.84 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.90 - 222.106.160.90 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.94 - 222.106.160.94 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.97 - 222.106.160.97 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.99 - 222.106.160.99 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.109 - 222.106.160.109 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.126 - 222.106.160.126 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.135 - 222.106.160.135 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.208 - 222.106.160.208 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.214 - 222.106.160.214 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.221 - 222.106.160.221 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.225 - 222.106.160.225 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.249 - 222.106.160.249 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.160.255 - 222.106.161.0 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.1 - 222.106.161.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.8 - 222.106.161.8 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.12 - 222.106.161.12 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.17 - 222.106.161.17 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.22 - 222.106.161.22 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.33 - 222.106.161.34 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.51 - 222.106.161.51 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.54 - 222.106.161.54 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.60 - 222.106.161.60 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.78 - 222.106.161.78 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.92 - 222.106.161.92 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.93 - 222.106.161.93 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.103 - 222.106.161.103 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 222.106.161.107 - 222.106.161.107 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |