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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 121.131.136.29
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36102
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;121.131.136.29.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 20:00:25 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 29.136.131.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 29.136.131.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
128.199.146.93 attack
2020-09-03T05:54:00.803413abusebot-4.cloudsearch.cf sshd[22273]: Invalid user guest from 128.199.146.93 port 51384
2020-09-03T05:54:00.809121abusebot-4.cloudsearch.cf sshd[22273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.146.93
2020-09-03T05:54:00.803413abusebot-4.cloudsearch.cf sshd[22273]: Invalid user guest from 128.199.146.93 port 51384
2020-09-03T05:54:02.937725abusebot-4.cloudsearch.cf sshd[22273]: Failed password for invalid user guest from 128.199.146.93 port 51384 ssh2
2020-09-03T06:03:52.147173abusebot-4.cloudsearch.cf sshd[22537]: Invalid user hadoop from 128.199.146.93 port 58616
2020-09-03T06:03:52.154205abusebot-4.cloudsearch.cf sshd[22537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.146.93
2020-09-03T06:03:52.147173abusebot-4.cloudsearch.cf sshd[22537]: Invalid user hadoop from 128.199.146.93 port 58616
2020-09-03T06:03:54.224230abusebot-4.cloudsearch.cf sshd[22537
...
2020-09-03 17:22:56
75.82.24.137 attackbotsspam
75.82.24.137 (US/United States/cpe-75-82-24-137.socal.res.rr.com), 4 distributed sshd attacks on account [admin] in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_DISTATTACK; Logs: Sep  2 12:43:37 internal2 sshd[8276]: Invalid user admin from 104.33.60.133 port 56280
Sep  2 12:43:37 internal2 sshd[8295]: Invalid user admin from 104.33.60.133 port 56301
Sep  2 12:43:54 internal2 sshd[8546]: Invalid user admin from 75.82.24.137 port 43254
Sep  2 12:43:35 internal2 sshd[8259]: Invalid user admin from 104.33.60.133 port 56206

IP Addresses Blocked:

104.33.60.133 (US/United States/cpe-104-33-60-133.socal.res.rr.com)
2020-09-03 17:07:34
61.177.172.168 attackbotsspam
Sep  3 11:13:41 router sshd[32138]: Failed password for root from 61.177.172.168 port 1141 ssh2
Sep  3 11:13:45 router sshd[32138]: Failed password for root from 61.177.172.168 port 1141 ssh2
Sep  3 11:13:49 router sshd[32138]: Failed password for root from 61.177.172.168 port 1141 ssh2
Sep  3 11:13:54 router sshd[32138]: Failed password for root from 61.177.172.168 port 1141 ssh2
...
2020-09-03 17:14:09
13.127.58.123 attackbots
reported through recidive - multiple failed attempts(SSH)
2020-09-03 17:04:16
138.204.225.120 attack
20/9/2@13:29:03: FAIL: Alarm-Network address from=138.204.225.120
20/9/2@13:29:04: FAIL: Alarm-Network address from=138.204.225.120
...
2020-09-03 17:06:45
195.206.105.217 attack
[02/Sep/2020:22:26:04 +0200] "GET /wp-config.php.original HTTP/1.1"
2020-09-03 16:44:19
93.39.184.17 attack
Invalid user admin from 93.39.184.17 port 37946
2020-09-03 16:46:31
188.120.239.4 attack
Failed password for invalid user dominic from 188.120.239.4 port 40980 ssh2
2020-09-03 17:19:49
139.198.5.138 attackspam
$f2bV_matches
2020-09-03 17:02:32
180.250.124.227 attackspam
Invalid user test from 180.250.124.227 port 58806
2020-09-03 17:17:27
177.129.206.128 attackbots
(smtpauth) Failed SMTP AUTH login from 177.129.206.128 (BR/Brazil/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-09-03 05:29:01 plain authenticator failed for ([177.129.206.128]) [177.129.206.128]: 535 Incorrect authentication data (set_id=sales@rm-co.com)
2020-09-03 17:11:36
45.154.255.68 attack
blogonese.net 45.154.255.68 [02/Sep/2020:18:43:41 +0200] "POST /xmlrpc.php HTTP/1.0" 301 493 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36"
blogonese.net 45.154.255.68 [02/Sep/2020:18:43:42 +0200] "POST /xmlrpc.php HTTP/1.0" 200 3595 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36"
2020-09-03 17:19:00
81.90.1.78 attack
1599065041 - 09/02/2020 18:44:01 Host: 81.90.1.78/81.90.1.78 Port: 445 TCP Blocked
2020-09-03 17:01:05
222.186.173.238 attackbots
Sep  3 10:28:17 vps639187 sshd\[5843\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
Sep  3 10:28:19 vps639187 sshd\[5843\]: Failed password for root from 222.186.173.238 port 30700 ssh2
Sep  3 10:28:23 vps639187 sshd\[5843\]: Failed password for root from 222.186.173.238 port 30700 ssh2
...
2020-09-03 16:40:28
106.12.210.115 attack
 TCP (SYN) 106.12.210.115:40518 -> port 14108, len 44
2020-09-03 17:25:27

Recently Reported IPs

121.130.254.153 121.131.16.243 121.131.116.211 121.131.214.62
121.131.198.208 121.131.94.149 114.254.214.208 121.132.114.153
121.132.114.104 121.131.116.242 121.132.113.167 121.131.94.165
114.255.243.160 235.239.80.229 171.127.215.25 114.26.201.185
114.27.161.98 114.30.76.63 121.138.138.64 121.138.145.38