Hosts in South Korea (KR)
Hosts located in South Korea (KR) indexed by QROS Explore — open ports, services, CVEs and TLS certificates.
Risk overview — this country
Aggregated from the 100 most-exposed indexed hosts of 1887 total. Severity reflects the worst known CVE on each host.
1887Affected hosts
98/100Avg exposure
1468Total CVEs
28%TLS coverage
Hosts by worst severity
Critical
100
High
0
Medium
0
Low
0
Negligible
0
Most exposed host
coldchain.ddns.net (3.38.154.143)
CriticalShowing 48 of 1887 hosts, ranked by risk score.
ec2-3-34-235-48.ap-northeast-2.compute.amazonaws.com (3.34.235.48)
South Korea · Incheon
3 open ports · 55 CVE · risk 100/100 · Critical
http, ssh
ec2-3-36-2-70.ap-northeast-2.compute.amazonaws.com (3.36.2.70)
South Korea · Incheon
1 open port · 54 CVE · risk 100/100 · Critical
http
85.155.177.201
South Korea · Yongsan-dong
1 open port · 3 CVE · risk 98/100 · Critical
ssh
ec2-3-35-108-30.ap-northeast-2.compute.amazonaws.com (3.35.108.30)
South Korea · Incheon
2 open ports · 48 CVE · risk 98/100 · Critical
http
coldchain.ddns.net (3.38.154.143)
South Korea · Incheon
7 open ports · 8 CVE · risk 98/100 · Critical
http, mqtt, mysql, ssh
ec2-3-38-193-143.ap-northeast-2.compute.amazonaws.com (3.38.193.143)
South Korea · Incheon
2 open ports · 25 CVE · risk 98/100 · Critical
http, ssh
ec2-3-34-80-244.ap-northeast-2.compute.amazonaws.com (3.34.80.244)
South Korea · Incheon
3 open ports · 21 CVE · risk 98/100 · Critical
http, ssh
ec2-3-35-250-235.ap-northeast-2.compute.amazonaws.com (3.35.250.235)
South Korea · Incheon
2 open ports · 5 CVE · risk 98/100 · Critical
http
ec2-3-38-205-247.ap-northeast-2.compute.amazonaws.com (3.38.205.247)
South Korea · Incheon
2 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-37-97-231.ap-northeast-2.compute.amazonaws.com (3.37.97.231)
South Korea · Incheon
2 open ports · 4 CVE · risk 98/100 · Critical
ssh
ec2-3-38-217-163.ap-northeast-2.compute.amazonaws.com (3.38.217.163)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-36-95-137.ap-northeast-2.compute.amazonaws.com (3.36.95.137)
South Korea · Incheon
1 open port · 25 CVE · risk 98/100 · Critical
ssh
ec2-3-39-194-122.ap-northeast-2.compute.amazonaws.com (3.39.194.122)
South Korea · Incheon
3 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-34-145-38.ap-northeast-2.compute.amazonaws.com (3.34.145.38)
South Korea · Incheon
1 open port · 25 CVE · risk 98/100 · Critical
ssh
ec2-3-34-210-98.ap-northeast-2.compute.amazonaws.com (3.34.210.98)
South Korea · Incheon
1 open port · 3 CVE · risk 98/100 · Critical
ssh
ec2-3-35-89-122.ap-northeast-2.compute.amazonaws.com (3.35.89.122)
South Korea · Incheon
2 open ports · 22 CVE · risk 98/100 · Critical
http, ssh
ec2-3-36-92-30.ap-northeast-2.compute.amazonaws.com (3.36.92.30)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-34-29-121.ap-northeast-2.compute.amazonaws.com (3.34.29.121)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-35-199-135.ap-northeast-2.compute.amazonaws.com (3.35.199.135)
South Korea · Incheon
3 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-38-107-233.ap-northeast-2.compute.amazonaws.com (3.38.107.233)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-35-49-116.ap-northeast-2.compute.amazonaws.com (3.35.49.116)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-38-206-172.ap-northeast-2.compute.amazonaws.com (3.38.206.172)
South Korea · Incheon
2 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-35-125-63.ap-northeast-2.compute.amazonaws.com (3.35.125.63)
South Korea · Incheon
2 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-39-239-139.ap-northeast-2.compute.amazonaws.com (3.39.239.139)
South Korea · Incheon
2 open ports · 28 CVE · risk 98/100 · Critical
http, ssh
dblive.net (3.38.86.109)
South Korea · Incheon
3 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-34-96-159.ap-northeast-2.compute.amazonaws.com (3.34.96.159)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-34-96-107.ap-northeast-2.compute.amazonaws.com (3.34.96.107)
South Korea · Incheon
2 open ports · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-38-191-141.ap-northeast-2.compute.amazonaws.com (3.38.191.141)
South Korea · Incheon
3 open ports · 28 CVE · risk 98/100 · Critical
http, ssh
ec2-3-35-16-249.ap-northeast-2.compute.amazonaws.com (3.35.16.249)
South Korea · Incheon
1 open port · 25 CVE · risk 98/100 · Critical
ssh
ec2-3-35-170-69.ap-northeast-2.compute.amazonaws.com (3.35.170.69)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-39-120-140.ap-northeast-2.compute.amazonaws.com (3.39.120.140)
South Korea · Incheon
1 open port · 22 CVE · risk 98/100 · Critical
ssh
ec2-3-35-205-104.ap-northeast-2.compute.amazonaws.com (3.35.205.104)
South Korea · Incheon
3 open ports · 8 CVE · risk 98/100 · Critical
http, ssh
ec2-3-36-189-113.ap-northeast-2.compute.amazonaws.com (3.36.189.113)
South Korea · Incheon
2 open ports · 83 CVE · risk 98/100 · Critical
http
ec2-3-36-122-1.ap-northeast-2.compute.amazonaws.com (3.36.122.1)
South Korea · Incheon
2 open ports · 28 CVE · risk 98/100 · Critical
http, ssh
ec2-3-36-32-69.ap-northeast-2.compute.amazonaws.com (3.36.32.69)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-38-99-122.ap-northeast-2.compute.amazonaws.com (3.38.99.122)
South Korea · Incheon
5 open ports · 5 CVE · risk 98/100 · Critical
http, mysql, postgres, ssh
ec2-3-34-105-103.ap-northeast-2.compute.amazonaws.com (3.34.105.103)
South Korea · Incheon
4 open ports · 36 CVE · risk 98/100 · Critical
http
ec2-3-39-224-242.ap-northeast-2.compute.amazonaws.com (3.39.224.242)
South Korea · Incheon
4 open ports · 25 CVE · risk 98/100 · Critical
sip, sip_tls, ssh
ec2-3-36-63-66.ap-northeast-2.compute.amazonaws.com (3.36.63.66)
South Korea · Incheon
2 open ports · 5 CVE · risk 98/100 · Critical
http, ssh
ec2-3-38-119-6.ap-northeast-2.compute.amazonaws.com (3.38.119.6)
South Korea · Incheon
1 open port · 22 CVE · risk 98/100 · Critical
ssh
ec2-3-36-97-130.ap-northeast-2.compute.amazonaws.com (3.36.97.130)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-34-58-252.ap-northeast-2.compute.amazonaws.com (3.34.58.252)
South Korea · Incheon
1 open port · 3 CVE · risk 98/100 · Critical
ssh
ec2-3-35-70-255.ap-northeast-2.compute.amazonaws.com (3.35.70.255)
South Korea · Incheon
4 open ports · 21 CVE · risk 98/100 · Critical
http, ssh
api.cardagent.kr (3.34.105.128)
South Korea · Incheon
3 open ports · 21 CVE · risk 98/100 · Critical
http, ssh
ec2-3-36-159-26.ap-northeast-2.compute.amazonaws.com (3.36.159.26)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-39-38-0.ap-northeast-2.compute.amazonaws.com (3.39.38.0)
South Korea · Incheon
1 open port · 5 CVE · risk 98/100 · Critical
ssh
ec2-3-38-101-174.ap-northeast-2.compute.amazonaws.com (3.38.101.174)
South Korea · Incheon
1 open port · 21 CVE · risk 98/100 · Critical
ssh
ec2-3-34-197-246.ap-northeast-2.compute.amazonaws.com (3.34.197.246)
South Korea · Incheon
3 open ports · 28 CVE · risk 98/100 · Critical
http, ssh
Search all hosts in South Korea in Explore
Open in Explore →