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:
IP Type Details Datetime
114.99.14.134 attackbots
MAIL: User Login Brute Force Attempt
2020-04-02 02:27:28
114.99.14.112 attack
Jan  9 13:50:43 mxgate1 postfix/postscreen[1105]: CONNECT from [114.99.14.112]:64732 to [176.31.12.44]:25
Jan  9 13:50:43 mxgate1 postfix/dnsblog[1164]: addr 114.99.14.112 listed by domain zen.spamhaus.org as 127.0.0.11
Jan  9 13:50:43 mxgate1 postfix/dnsblog[1164]: addr 114.99.14.112 listed by domain zen.spamhaus.org as 127.0.0.4
Jan  9 13:50:43 mxgate1 postfix/dnsblog[1163]: addr 114.99.14.112 listed by domain cbl.abuseat.org as 127.0.0.2
Jan  9 13:50:43 mxgate1 postfix/dnsblog[1160]: addr 114.99.14.112 listed by domain b.barracudacentral.org as 127.0.0.2
Jan  9 13:50:44 mxgate1 postfix/postscreen[1105]: PREGREET 14 after 0.26 from [114.99.14.112]:64732: EHLO IHR2prK

Jan  9 13:50:44 mxgate1 postfix/postscreen[1105]: DNSBL rank 4 for [114.99.14.112]:64732
Jan  9 13:50:45 mxgate1 postfix/postscreen[1105]: NOQUEUE: reject: RCPT from [114.99.14.112]:64732: 550 5.7.1 Service unavailable; client [114.99.14.112] blocked using zen.spamhaus.org; from=x@x helo=


........
-----------------------------------
2020-01-10 03:18:58
114.99.14.200 attackbots
Sep  1 23:09:32 eola postfix/smtpd[1010]: connect from unknown[114.99.14.200]
Sep  1 23:09:33 eola postfix/smtpd[1010]: NOQUEUE: reject: RCPT from unknown[114.99.14.200]: 504 5.5.2 : Helo command rejected: need fully-qualified hostname; from=x@x helo=<55vCdI>
Sep  1 23:09:33 eola postfix/smtpd[1010]: disconnect from unknown[114.99.14.200] ehlo=1 mail=1 rcpt=0/1 quhostname=1 commands=3/4
Sep  1 23:09:34 eola postfix/smtpd[1010]: connect from unknown[114.99.14.200]
Sep  1 23:09:34 eola postfix/smtpd[1010]: lost connection after AUTH from unknown[114.99.14.200]
Sep  1 23:09:34 eola postfix/smtpd[1010]: disconnect from unknown[114.99.14.200] ehlo=1 auth=0/1 commands=1/2
Sep  1 23:09:35 eola postfix/smtpd[1010]: connect from unknown[114.99.14.200]
Sep  1 23:09:35 eola postfix/smtpd[1010]: lost connection after AUTH from unknown[114.99.14.200]
Sep  1 23:09:35 eola postfix/smtpd[1010]: disconnect from unknown[114.99.14.200] ehlo=1 auth=0/1 commands=1/2
Sep  1 23:09:35 eola ........
-------------------------------
2019-09-02 12:36:21
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.99.14.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40589
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.99.14.8.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 06 12:18:53 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 8.14.99.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 8.14.99.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
54.38.185.87 attackspambots
(sshd) Failed SSH login from 54.38.185.87 (FR/France/87.ip-54-38-185.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 23 15:53:30 server2 sshd[18616]: Invalid user user from 54.38.185.87 port 49314
Oct 23 15:53:31 server2 sshd[18616]: Failed password for invalid user user from 54.38.185.87 port 49314 ssh2
Oct 23 16:02:59 server2 sshd[18884]: Failed password for root from 54.38.185.87 port 34312 ssh2
Oct 23 16:07:19 server2 sshd[18996]: Invalid user dongguanidc from 54.38.185.87 port 53634
Oct 23 16:07:20 server2 sshd[18996]: Failed password for invalid user dongguanidc from 54.38.185.87 port 53634 ssh2
2019-10-24 00:14:44
106.12.100.184 attack
Oct 23 09:47:31 firewall sshd[24037]: Invalid user uno8 from 106.12.100.184
Oct 23 09:47:34 firewall sshd[24037]: Failed password for invalid user uno8 from 106.12.100.184 port 36544 ssh2
Oct 23 09:52:39 firewall sshd[24125]: Invalid user secor from 106.12.100.184
...
2019-10-24 00:05:12
170.238.46.6 attackbots
Oct 23 17:48:21 MK-Soft-VM5 sshd[7288]: Failed password for root from 170.238.46.6 port 44694 ssh2
...
2019-10-24 00:22:19
222.186.180.147 attackbotsspam
2019-10-23T22:58:37.948540enmeeting.mahidol.ac.th sshd\[32113\]: User root from 222.186.180.147 not allowed because not listed in AllowUsers
2019-10-23T22:58:39.208853enmeeting.mahidol.ac.th sshd\[32113\]: Failed none for invalid user root from 222.186.180.147 port 56190 ssh2
2019-10-23T22:58:40.577158enmeeting.mahidol.ac.th sshd\[32113\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147  user=root
...
2019-10-23 23:59:04
198.108.66.93 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-24 00:18:08
139.198.122.76 attackspambots
Oct 23 15:50:22 bouncer sshd\[24633\]: Invalid user podcast from 139.198.122.76 port 51658
Oct 23 15:50:22 bouncer sshd\[24633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.122.76 
Oct 23 15:50:25 bouncer sshd\[24633\]: Failed password for invalid user podcast from 139.198.122.76 port 51658 ssh2
...
2019-10-24 00:14:57
36.66.149.211 attackbots
Oct 23 12:04:10 TORMINT sshd\[25040\]: Invalid user user from 36.66.149.211
Oct 23 12:04:10 TORMINT sshd\[25040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.66.149.211
Oct 23 12:04:12 TORMINT sshd\[25040\]: Failed password for invalid user user from 36.66.149.211 port 51780 ssh2
...
2019-10-24 00:17:47
210.210.175.63 attack
2019-10-23T14:44:33.366373abusebot-4.cloudsearch.cf sshd\[30519\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.210.175.63  user=root
2019-10-24 00:08:35
187.141.50.219 attackspam
Invalid user yn from 187.141.50.219 port 51754
2019-10-23 23:58:28
118.41.11.46 attack
2019-10-23T15:46:53.938423abusebot-5.cloudsearch.cf sshd\[6310\]: Invalid user rakesh from 118.41.11.46 port 36242
2019-10-24 00:03:09
106.12.211.247 attack
SSH bruteforce (Triggered fail2ban)
2019-10-24 00:14:09
212.225.144.19 attackspam
Port Scan
2019-10-24 00:06:41
122.3.88.147 attack
2019-10-23T17:45:06.922322  sshd[13777]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.3.88.147  user=root
2019-10-23T17:45:08.912025  sshd[13777]: Failed password for root from 122.3.88.147 port 46544 ssh2
2019-10-23T17:51:30.558298  sshd[13889]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.3.88.147  user=root
2019-10-23T17:51:32.598647  sshd[13889]: Failed password for root from 122.3.88.147 port 15418 ssh2
2019-10-23T17:57:52.629992  sshd[13927]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.3.88.147  user=root
2019-10-23T17:57:55.116279  sshd[13927]: Failed password for root from 122.3.88.147 port 41720 ssh2
...
2019-10-24 00:00:33
89.248.160.76 attackspam
Brute Force attack - banned by Fail2Ban
2019-10-24 00:18:23
222.170.168.90 attackbotsspam
ssh failed login
2019-10-23 23:56:45

Recently Reported IPs

117.215.200.237 117.215.201.103 117.215.201.189 117.215.201.219
117.215.201.122 117.215.202.170 117.215.201.14 117.215.202.13
117.215.202.29 114.99.14.80 117.215.201.52 117.215.202.249
117.215.203.126 117.215.202.105 117.215.203.235 117.215.203.168
117.216.105.204 117.215.203.20 117.215.203.241 87.246.159.231