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

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 <<>> 122.138.137.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17243
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;122.138.137.21.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 01:23:57 CST 2022
;; MSG SIZE  rcvd: 107
Host info
21.137.138.122.in-addr.arpa domain name pointer 21.137.138.122.adsl-pool.jlccptt.net.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.137.138.122.in-addr.arpa	name = 21.137.138.122.adsl-pool.jlccptt.net.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
112.85.42.238 attack
Sep 10 13:30:38 h2177944 sshd\[14070\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.238  user=root
Sep 10 13:30:40 h2177944 sshd\[14070\]: Failed password for root from 112.85.42.238 port 15052 ssh2
Sep 10 13:30:42 h2177944 sshd\[14070\]: Failed password for root from 112.85.42.238 port 15052 ssh2
Sep 10 13:30:44 h2177944 sshd\[14070\]: Failed password for root from 112.85.42.238 port 15052 ssh2
...
2019-09-10 19:39:39
106.52.142.17 attackbotsspam
Sep 10 13:35:27 ubuntu-2gb-nbg1-dc3-1 sshd[26893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.142.17
Sep 10 13:35:29 ubuntu-2gb-nbg1-dc3-1 sshd[26893]: Failed password for invalid user uftp from 106.52.142.17 port 58620 ssh2
...
2019-09-10 19:36:49
197.51.129.126 attackbotsspam
Port Scan: TCP/23
2019-09-10 19:20:03
162.243.144.22 attackbotsspam
Aug 29 17:19:18 mercury kernel: [UFW ALLOW] IN=eth0 OUT= MAC=f2:3c:91:bc:4d:f8:84:78:ac:0d:8f:41:08:00 SRC=162.243.144.22 DST=109.74.200.221 LEN=76 TOS=0x00 PREC=0x00 TTL=245 ID=54321 PROTO=UDP SPT=48915 DPT=123 LEN=56 
...
2019-09-10 19:56:38
27.14.44.163 attackspambots
" "
2019-09-10 19:54:37
128.199.224.215 attackspambots
Sep 10 01:43:16 auw2 sshd\[10832\]: Invalid user admin from 128.199.224.215
Sep 10 01:43:16 auw2 sshd\[10832\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.224.215
Sep 10 01:43:19 auw2 sshd\[10832\]: Failed password for invalid user admin from 128.199.224.215 port 39894 ssh2
Sep 10 01:49:35 auw2 sshd\[11372\]: Invalid user test1 from 128.199.224.215
Sep 10 01:49:35 auw2 sshd\[11372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.224.215
2019-09-10 20:05:01
162.244.80.114 attackspam
Aug 21 09:48:27 mercury kernel: [UFW ALLOW] IN=eth0 OUT= MAC=f2:3c:91:bc:4d:f8:84:78:ac:0d:8f:41:08:00 SRC=162.244.80.114 DST=109.74.200.221 LEN=37 TOS=0x00 PREC=0x00 TTL=56 ID=51980 DF PROTO=UDP SPT=39453 DPT=123 LEN=17 
...
2019-09-10 19:48:18
115.29.3.34 attackbots
Reported by AbuseIPDB proxy server.
2019-09-10 20:01:57
113.172.204.255 attackbots
2019-08-08T13:02:14.300Z CLOSE host=113.172.204.255 port=46210 fd=5 time=50.029 bytes=56
...
2019-09-10 20:05:52
123.148.208.98 attack
[Wed Aug 14 05:36:22.652676 2019] [access_compat:error] [pid 5007] [client 123.148.208.98:56781] AH01797: client denied by server configuration: /var/www/html/josh/wp-login.php
...
2019-09-10 19:45:20
117.50.92.160 attackspam
Sep 10 01:54:36 web1 sshd\[20188\]: Invalid user www from 117.50.92.160
Sep 10 01:54:36 web1 sshd\[20188\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.92.160
Sep 10 01:54:38 web1 sshd\[20188\]: Failed password for invalid user www from 117.50.92.160 port 45670 ssh2
Sep 10 01:56:33 web1 sshd\[20965\]: Invalid user 123 from 117.50.92.160
Sep 10 01:56:33 web1 sshd\[20965\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.92.160
2019-09-10 20:09:59
170.55.25.142 attackbots
Port Scan: UDP/137
2019-09-10 19:23:38
162.244.81.160 attackspam
May 28 02:37:51 mercury kernel: [UFW ALLOW] IN=eth0 OUT= MAC=f2:3c:91:bc:4d:f8:84:78:ac:0d:8f:41:08:00 SRC=162.244.81.160 DST=109.74.200.221 LEN=220 TOS=0x00 PREC=0x00 TTL=247 ID=54321 PROTO=UDP SPT=48012 DPT=123 LEN=200 
...
2019-09-10 19:38:35
104.248.161.244 attackspam
Sep 10 01:24:41 kapalua sshd\[21547\]: Invalid user deploy from 104.248.161.244
Sep 10 01:24:41 kapalua sshd\[21547\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.161.244
Sep 10 01:24:44 kapalua sshd\[21547\]: Failed password for invalid user deploy from 104.248.161.244 port 47234 ssh2
Sep 10 01:30:45 kapalua sshd\[22116\]: Invalid user teamspeak from 104.248.161.244
Sep 10 01:30:45 kapalua sshd\[22116\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.161.244
2019-09-10 19:37:17
113.189.235.57 attackspam
2019-08-28T05:10:57.990Z CLOSE host=113.189.235.57 port=59366 fd=6 time=960.184 bytes=1586
...
2019-09-10 19:44:02

Recently Reported IPs

122.138.137.194 122.138.137.214 122.138.137.220 122.138.137.241
122.138.137.245 122.138.137.247 122.138.137.28 122.138.137.37
122.138.137.39 122.138.137.40 122.138.137.47 122.138.137.5
122.138.137.77 122.138.137.89 139.56.129.226 122.138.137.91
122.138.137.94 122.138.138.0 122.138.138.111 122.138.138.121