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: unknown

Region: unknown

Country: Korea Republic of

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:
IP Type Details Datetime
121.169.34.103 attack
Lines containing failures of 121.169.34.103
Oct  5 22:28:14 kopano sshd[17644]: Bad protocol version identification 'GET / HTTP/1.1' from 121.169.34.103 port 55203
Oct  5 22:28:22 kopano sshd[17645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.169.34.103  user=r.r
Oct  5 22:28:24 kopano sshd[17645]: Failed password for r.r from 121.169.34.103 port 55220 ssh2
Oct  5 22:28:26 kopano sshd[17645]: Connection closed by authenticating user r.r 121.169.34.103 port 55220 [preauth]
Oct  5 22:28:32 kopano sshd[18412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.169.34.103  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=121.169.34.103
2020-10-07 06:54:40
121.169.34.103 attack
Lines containing failures of 121.169.34.103
Oct  5 22:28:14 kopano sshd[17644]: Bad protocol version identification 'GET / HTTP/1.1' from 121.169.34.103 port 55203
Oct  5 22:28:22 kopano sshd[17645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.169.34.103  user=r.r
Oct  5 22:28:24 kopano sshd[17645]: Failed password for r.r from 121.169.34.103 port 55220 ssh2
Oct  5 22:28:26 kopano sshd[17645]: Connection closed by authenticating user r.r 121.169.34.103 port 55220 [preauth]
Oct  5 22:28:32 kopano sshd[18412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.169.34.103  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=121.169.34.103
2020-10-06 23:14:32
121.169.34.103 attackspam
Lines containing failures of 121.169.34.103
Oct  5 22:28:14 kopano sshd[17644]: Bad protocol version identification 'GET / HTTP/1.1' from 121.169.34.103 port 55203
Oct  5 22:28:22 kopano sshd[17645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.169.34.103  user=r.r
Oct  5 22:28:24 kopano sshd[17645]: Failed password for r.r from 121.169.34.103 port 55220 ssh2
Oct  5 22:28:26 kopano sshd[17645]: Connection closed by authenticating user r.r 121.169.34.103 port 55220 [preauth]
Oct  5 22:28:32 kopano sshd[18412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.169.34.103  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=121.169.34.103
2020-10-06 15:02:21
121.169.34.151 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-16 10:34:31
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 121.169.34.172
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10905
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;121.169.34.172.			IN	A

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

;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 15 07:41:04 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 172.34.169.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 172.34.169.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
59.8.74.149 attackspambots
Unauthorized connection attempt detected from IP address 59.8.74.149 to port 23 [J]
2020-01-19 15:15:35
125.99.114.66 attack
Unauthorized connection attempt detected from IP address 125.99.114.66 to port 3389 [J]
2020-01-19 15:07:20
202.107.148.203 attackbots
Unauthorized connection attempt detected from IP address 202.107.148.203 to port 8080 [J]
2020-01-19 14:58:31
77.42.88.218 attackbotsspam
Unauthorized connection attempt detected from IP address 77.42.88.218 to port 23 [J]
2020-01-19 15:14:50
182.55.43.72 attackspambots
Unauthorized connection attempt detected from IP address 182.55.43.72 to port 5555 [J]
2020-01-19 15:30:15
185.183.243.150 attackbots
Unauthorized connection attempt detected from IP address 185.183.243.150 to port 2220 [J]
2020-01-19 15:01:44
58.249.97.161 attackspambots
Unauthorized connection attempt detected from IP address 58.249.97.161 to port 3097 [J]
2020-01-19 15:16:04
77.127.57.225 attackbots
Unauthorized connection attempt detected from IP address 77.127.57.225 to port 85 [J]
2020-01-19 15:14:31
188.242.83.205 attackspambots
Unauthorized connection attempt detected from IP address 188.242.83.205 to port 81 [J]
2020-01-19 14:59:52
45.84.185.182 attackbotsspam
Unauthorized connection attempt detected from IP address 45.84.185.182 to port 23 [J]
2020-01-19 15:17:37
123.179.7.49 attack
Unauthorized connection attempt detected from IP address 123.179.7.49 to port 443 [T]
2020-01-19 15:34:10
41.190.63.174 attackspam
Unauthorized connection attempt detected from IP address 41.190.63.174 to port 8080 [J]
2020-01-19 15:18:19
116.26.175.75 attack
Unauthorized connection attempt detected from IP address 116.26.175.75 to port 2323 [J]
2020-01-19 15:08:54
82.102.83.54 attackbotsspam
Unauthorized connection attempt detected from IP address 82.102.83.54 to port 5555 [J]
2020-01-19 15:13:23
220.132.0.42 attackspam
Unauthorized connection attempt detected from IP address 220.132.0.42 to port 4567 [J]
2020-01-19 15:24:26

Recently Reported IPs

68.56.143.156 189.123.126.254 113.131.152.33 185.141.63.4
211.57.150.210 111.43.114.50 114.216.168.19 111.17.209.155
1.14.64.80 112.46.68.122 83.142.52.19 66.198.210.142
20.0.24.45 83.171.252.117 1.0.136.136 110.77.161.34
114.221.141.243 114.236.1.225 89.238.133.116 193.233.230.19