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

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

;; QUESTION SECTION:
;116.229.149.89.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 19:14:53 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 89.149.229.116.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 89.149.229.116.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
37.6.224.22 attackspam
port scan and connect, tcp 23 (telnet)
2019-06-24 10:17:53
173.89.120.26 attackspam
19/6/23@15:53:26: FAIL: IoT-SSH address from=173.89.120.26
...
2019-06-24 10:23:18
119.158.108.84 attack
Hit on /wp-login.php
2019-06-24 10:09:33
121.54.174.240 attackspambots
Blocking for trying to access an exploit file: /test.php
2019-06-24 10:05:59
193.32.163.123 attackbotsspam
Jun 20 03:53:11 mail2 sshd[3002]: Invalid user admin from 193.32.163.123 port 54217
Jun 20 03:53:11 mail2 sshd[3001]: Invalid user admin from 193.32.163.123 port 53780
Jun 20 03:53:11 mail2 sshd[3002]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.32.163.123
Jun 20 03:53:11 mail2 sshd[3001]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.32.163.123
Jun 20 03:53:13 mail2 sshd[3002]: Failed password for invalid user admin from 193.32.163.123 port 54217 ssh2
Jun 20 03:53:13 mail2 sshd[3001]: Failed password for invalid user admin from 193.32.163.123 port 53780 ssh2
Jun 20 18:16:47 mail2 sshd[7487]: Invalid user admin from 193.32.163.123 port 41484
Jun 20 18:16:47 mail2 sshd[7487]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.32.163.123
Jun 20 18:16:47 mail2 sshd[7488]: Invalid user admin from 193.32.163.123 port 52675
Jun 20 18:16:47 mai........
-------------------------------
2019-06-24 09:56:46
185.220.101.25 attackbotsspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.25  user=root
Failed password for root from 185.220.101.25 port 37529 ssh2
Failed password for root from 185.220.101.25 port 37529 ssh2
Failed password for root from 185.220.101.25 port 37529 ssh2
Failed password for root from 185.220.101.25 port 37529 ssh2
2019-06-24 09:54:00
197.34.178.31 attack
1561319755 - 06/24/2019 02:55:55 Host: host-197.34.178.31.tedata.net/197.34.178.31 Port: 23 TCP Blocked
...
2019-06-24 09:51:18
185.220.101.29 attackspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.29  user=root
Failed password for root from 185.220.101.29 port 35777 ssh2
Failed password for root from 185.220.101.29 port 35777 ssh2
Failed password for root from 185.220.101.29 port 35777 ssh2
Failed password for root from 185.220.101.29 port 35777 ssh2
2019-06-24 09:54:31
113.240.190.248 attackspambots
FTP login brute force attempts.
Time: Sun Jun 23. 14:38:12 2019 +0200
IP: 113.240.190.248 (CN/China/-)
Blocked: Permanent Block

Log entries:
Jun 23 14:36:52 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:01 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:12 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:20 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:27 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:35 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:43 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
Jun 23 14:37:50 vserv pure-ftpd: (?@113.240.190.248) [WARNING] Authentication failed for user [removed]
....
2019-06-24 10:19:03
157.230.28.16 attackbots
$f2bV_matches
2019-06-24 10:12:37
185.220.101.21 attackspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.21  user=root
Failed password for root from 185.220.101.21 port 36659 ssh2
Failed password for root from 185.220.101.21 port 36659 ssh2
Failed password for root from 185.220.101.21 port 36659 ssh2
Failed password for root from 185.220.101.21 port 36659 ssh2
2019-06-24 10:24:46
37.212.11.57 attackbots
utm - spam
2019-06-24 10:11:04
186.224.171.22 attack
SMTP-sasl brute force
...
2019-06-24 10:08:42
77.247.110.194 attack
SIP Server BruteForce Attack
2019-06-24 09:50:45
185.145.203.195 attackbots
Brute force attempt
2019-06-24 10:26:37

Recently Reported IPs

116.228.90.34 142.233.12.31 114.106.137.49 116.229.177.152
116.229.171.254 116.229.76.154 116.229.60.144 116.23.122.40
116.229.80.206 116.23.126.209 116.23.126.64 116.23.127.161
116.23.127.214 116.229.80.190 114.106.137.52 116.23.154.172
116.23.154.161 116.23.154.203 116.23.155.176 116.23.155.249