Russian
Search for "Korea Telecom"
| IP Pool | Country | State / Region | City | Coordinates | Timezone |
|---|---|---|---|---|---|
| 221.163.173.128 - 221.163.173.231 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.173.240 - 221.163.173.247 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.174.0 - 221.163.174.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.175.0 - 221.163.176.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.176.192 - 221.163.177.143 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.177.160 - 221.163.177.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.178.0 - 221.163.183.143 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.183.176 - 221.163.183.207 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.186.64 - 221.163.186.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.188.0 - 221.163.188.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.189.0 - 221.163.189.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.190.0 - 221.163.190.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.192.96 - 221.163.192.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.195.128 - 221.163.195.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.199.64 - 221.163.199.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.199.128 - 221.163.199.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.199.192 - 221.163.199.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.200.48 - 221.163.200.55 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.200.96 - 221.163.200.159 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.200.208 - 221.163.200.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.200.232 - 221.163.201.15 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.201.64 - 221.163.201.79 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.201.128 - 221.163.201.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.202.16 - 221.163.202.47 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.202.64 - 221.163.202.79 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.202.112 - 221.163.202.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.202.144 - 221.163.202.175 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.202.208 - 221.163.203.47 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.203.64 - 221.163.203.159 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.203.176 - 221.163.203.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.204.0 - 221.163.205.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.205.128 - 221.163.205.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.206.8 - 221.163.206.23 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.206.32 - 221.163.206.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.206.128 - 221.163.206.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.207.0 - 221.163.207.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.207.128 - 221.163.207.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.208.0 - 221.163.209.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.210.128 - 221.163.211.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.211.96 - 221.163.211.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.211.160 - 221.163.211.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.212.36 - 221.163.212.39 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.212.64 - 221.163.212.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.212.192 - 221.163.212.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.212.240 - 221.163.212.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.213.0 - 221.163.213.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.213.128 - 221.163.214.31 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.218.32 - 221.163.219.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.220.64 - 221.163.220.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.222.0 - 221.163.223.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.225.0 - 221.163.225.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.225.192 - 221.163.225.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.226.128 - 221.163.226.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.227.128 - 221.163.227.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.229.0 - 221.163.229.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.230.128 - 221.163.230.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.231.128 - 221.163.232.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.233.0 - 221.163.233.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.234.0 - 221.163.235.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.237.0 - 221.163.237.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.237.128 - 221.163.238.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.238.192 - 221.163.239.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.240.0 - 221.163.240.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.241.64 - 221.163.241.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.242.32 - 221.163.242.47 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.242.64 - 221.163.242.79 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.242.96 - 221.163.242.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.242.144 - 221.163.242.175 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.242.192 - 221.163.242.207 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.242.224 - 221.163.242.239 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.243.0 - 221.163.243.47 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.243.64 - 221.163.243.111 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.243.240 - 221.163.243.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.244.0 - 221.163.246.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.247.0 - 221.163.247.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.247.128 - 221.163.247.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.248.0 - 221.163.248.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.249.0 - 221.163.250.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.251.64 - 221.163.251.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.251.192 - 221.163.253.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.163.254.32 - 221.163.255.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.6.0 - 221.164.6.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.8.0 - 221.164.8.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.10.128 - 221.164.10.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.12.128 - 221.164.12.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.13.160 - 221.164.13.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.14.128 - 221.164.14.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.16.0 - 221.164.18.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.20.0 - 221.164.20.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.22.0 - 221.164.22.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.24.0 - 221.164.24.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.24.192 - 221.164.25.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.28.0 - 221.164.28.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.30.64 - 221.164.30.79 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.32.0 - 221.164.32.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.34.0 - 221.164.34.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.35.128 - 221.164.35.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.39.128 - 221.164.39.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.43.192 - 221.164.43.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 221.164.44.64 - 221.164.44.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |