Russian
Search for "Korea Telecom"
| IP Pool | Country | State / Region | City | Coordinates | Timezone |
|---|---|---|---|---|---|
| 220.79.95.128 - 220.79.95.159 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.95.176 - 220.79.95.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.96.0 - 220.79.96.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.96.112 - 220.79.96.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.96.192 - 220.79.96.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.97.0 - 220.79.97.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.98.0 - 220.79.98.31 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.98.32 - 220.79.98.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.98.96 - 220.79.98.119 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.98.144 - 220.79.98.159 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.98.176 - 220.79.98.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.99.0 - 220.79.103.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.104.0 - 220.79.104.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.106.0 - 220.79.107.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.108.0 - 220.79.108.7 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.108.16 - 220.79.108.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.109.0 - 220.79.110.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.110.255 - 220.79.110.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.111.64 - 220.79.111.111 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.112.128 - 220.79.112.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.113.0 - 220.79.113.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.115.64 - 220.79.115.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.116.0 - 220.79.116.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.117.0 - 220.79.118.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.119.64 - 220.79.119.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.120.0 - 220.79.120.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.121.0 - 220.79.121.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.121.64 - 220.79.121.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.121.128 - 220.79.121.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.122.128 - 220.79.122.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.123.0 - 220.79.123.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.123.128 - 220.79.123.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.124.0 - 220.79.124.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.125.96 - 220.79.125.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.126.0 - 220.79.127.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.128.0 - 220.79.128.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.128.64 - 220.79.128.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.128.128 - 220.79.128.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.129.128 - 220.79.130.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.130.160 - 220.79.130.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.130.224 - 220.79.130.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.131.64 - 220.79.131.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.132.0 - 220.79.132.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.135.0 - 220.79.135.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.136.0 - 220.79.136.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.137.0 - 220.79.140.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.142.0 - 220.79.144.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.146.128 - 220.79.146.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.146.192 - 220.79.147.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.147.192 - 220.79.147.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.148.128 - 220.79.148.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.149.192 - 220.79.149.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.150.0 - 220.79.150.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.153.0 - 220.79.154.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.154.224 - 220.79.154.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.155.192 - 220.79.157.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.158.192 - 220.79.158.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.159.128 - 220.79.160.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.160.96 - 220.79.160.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.165.0 - 220.79.165.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.165.96 - 220.79.165.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.166.128 - 220.79.166.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.167.192 - 220.79.173.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.174.0 - 220.79.175.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.176.16 - 220.79.176.31 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.176.48 - 220.79.176.223 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.177.0 - 220.79.177.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.177.96 - 220.79.179.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.180.128 - 220.79.181.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.182.128 - 220.79.182.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.186.0 - 220.79.186.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.188.0 - 220.79.192.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.193.0 - 220.79.194.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.194.127 - 220.79.194.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.194.133 - 220.79.194.133 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.194.138 - 220.79.194.138 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.194.179 - 220.79.194.179 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.194.255 - 220.79.194.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.195.160 - 220.79.195.167 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.196.0 - 220.79.197.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.198.0 - 220.79.200.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.201.0 - 220.79.203.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.204.0 - 220.79.211.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.213.0 - 220.79.213.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.214.0 - 220.79.214.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.215.0 - 220.79.215.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.216.0 - 220.79.216.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.221.0 - 220.79.221.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.221.55 - 220.79.221.55 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.221.69 - 220.79.221.69 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.221.107 - 220.79.221.107 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.221.255 - 220.79.222.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.223.0 - 220.79.228.1 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.44 - 220.79.228.44 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.47 - 220.79.228.47 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.49 - 220.79.228.49 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.77 - 220.79.228.77 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.87 - 220.79.228.87 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.92 - 220.79.228.92 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 220.79.228.95 - 220.79.228.95 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |