Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Seoul

Region: Seoul Special City

Country: South Korea

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 121.160.134.169
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51259
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;121.160.134.169.		IN	A

;; AUTHORITY SECTION:
.			447	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2023021601 1800 900 604800 86400

;; Query time: 78 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 17 06:22:09 CST 2023
;; MSG SIZE  rcvd: 108
Host info
Host 169.134.160.121.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 169.134.160.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
70.132.43.89 attack
Automatic report generated by Wazuh
2020-01-24 03:05:11
122.228.19.79 attackspambots
firewall-block, port(s): 84/tcp
2020-01-24 02:37:16
118.70.216.153 attack
kp-sea2-01 recorded 2 login violations from 118.70.216.153 and was blocked at 2020-01-23 16:34:56. 118.70.216.153 has been blocked on 4 previous occasions. 118.70.216.153's first attempt was recorded at 2020-01-23 14:52:05
2020-01-24 02:39:08
81.249.131.18 attackspam
Jan 23 18:41:24 DAAP sshd[8009]: Invalid user mon from 81.249.131.18 port 52924
Jan 23 18:41:24 DAAP sshd[8009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.249.131.18
Jan 23 18:41:24 DAAP sshd[8009]: Invalid user mon from 81.249.131.18 port 52924
Jan 23 18:41:26 DAAP sshd[8009]: Failed password for invalid user mon from 81.249.131.18 port 52924 ssh2
Jan 23 18:42:37 DAAP sshd[8016]: Invalid user moria from 81.249.131.18 port 36290
...
2020-01-24 02:26:27
138.197.213.233 attack
Jan 23 18:21:20 lnxmail61 sshd[25166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.213.233
2020-01-24 02:39:29
37.145.195.15 attackspambots
honeypot forum registration (user=Jamesjed; email=gdnbk1wvl@mail.ru)
2020-01-24 02:45:10
138.68.96.161 attack
Jan 23 19:38:11 localhost sshd\[6645\]: Invalid user mu from 138.68.96.161 port 35616
Jan 23 19:38:11 localhost sshd\[6645\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.96.161
Jan 23 19:38:13 localhost sshd\[6645\]: Failed password for invalid user mu from 138.68.96.161 port 35616 ssh2
2020-01-24 02:42:00
222.186.180.6 attackbotsspam
Jan 23 19:33:53 dedicated sshd[20006]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.6  user=root
Jan 23 19:33:55 dedicated sshd[20006]: Failed password for root from 222.186.180.6 port 64226 ssh2
2020-01-24 02:42:38
80.211.190.224 attackspambots
2020-01-23T18:55:58.866054shield sshd\[6690\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.190.224  user=root
2020-01-23T18:56:00.481655shield sshd\[6690\]: Failed password for root from 80.211.190.224 port 47892 ssh2
2020-01-23T18:58:06.248289shield sshd\[7092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.190.224  user=root
2020-01-23T18:58:07.771436shield sshd\[7092\]: Failed password for root from 80.211.190.224 port 38118 ssh2
2020-01-23T19:00:06.861825shield sshd\[7674\]: Invalid user dm from 80.211.190.224 port 56562
2020-01-24 03:00:55
181.174.81.245 attackbots
Jan 23 16:07:43 unicornsoft sshd\[9568\]: Invalid user arlindo from 181.174.81.245
Jan 23 16:07:43 unicornsoft sshd\[9568\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.174.81.245
Jan 23 16:07:45 unicornsoft sshd\[9568\]: Failed password for invalid user arlindo from 181.174.81.245 port 44265 ssh2
2020-01-24 02:29:44
103.83.36.101 attack
WordPress wp-login brute force :: 103.83.36.101 0.276 - [23/Jan/2020:16:07:48  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1806 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2020-01-24 02:28:42
54.71.10.34 attackbotsspam
Unauthorized connection attempt detected from IP address 54.71.10.34 to port 1433 [J]
2020-01-24 02:58:51
89.163.209.26 attackspambots
Unauthorized connection attempt detected from IP address 89.163.209.26 to port 2220 [J]
2020-01-24 02:54:42
14.29.205.220 attackspambots
2020-01-23T11:29:54.204408-07:00 suse-nuc sshd[26161]: Invalid user user from 14.29.205.220 port 34196
...
2020-01-24 02:48:50
14.171.225.131 attack
20/1/23@12:56:41: FAIL: Alarm-Network address from=14.171.225.131
20/1/23@12:56:41: FAIL: Alarm-Network address from=14.171.225.131
...
2020-01-24 02:41:28

Recently Reported IPs

52.127.212.138 23.109.87.106 25.219.201.118 84.95.84.65
198.170.127.13 100.7.253.72 178.31.243.118 34.153.219.214
39.110.194.67 173.178.105.45 164.43.14.226 1.46.28.209
173.82.196.25 1.20.70.16 43.159.247.1 116.75.89.157
146.202.77.230 61.74.3.175 106.255.220.138 36.50.112.149