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

Region: Anhui

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.0.204 attackbots
MAIL: User Login Brute Force Attempt
2020-03-12 06:36:16
114.99.0.62 attackbots
Lines containing failures of 114.99.0.62


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=114.99.0.62
2020-02-26 10:31:16
114.99.0.3 attack
Unauthorized connection attempt detected from IP address 114.99.0.3 to port 6656 [T]
2020-01-30 14:48:32
114.99.0.140 attack
Unauthorized connection attempt detected from IP address 114.99.0.140 to port 6656 [T]
2020-01-27 04:32:38
114.99.0.120 attackbots
Brute force attempt
2020-01-11 05:46:41
114.99.0.30 attack
Brute force attempt
2020-01-10 07:21:34
114.99.0.221 attackspambots
Nov  9 01:05:41 eola postfix/smtpd[31453]: connect from unknown[114.99.0.221]
Nov  9 01:05:41 eola postfix/smtpd[31453]: NOQUEUE: reject: RCPT from unknown[114.99.0.221]: 504 5.5.2 : Helo command rejected: need fully-qualified hostname; from=x@x helo=<36hp89k>
Nov  9 01:05:41 eola postfix/smtpd[31453]: disconnect from unknown[114.99.0.221] ehlo=1 mail=1 rcpt=0/1 quhostname=1 commands=3/4
Nov  9 01:05:42 eola postfix/smtpd[31453]: connect from unknown[114.99.0.221]
Nov  9 01:05:43 eola postfix/smtpd[31453]: lost connection after AUTH from unknown[114.99.0.221]
Nov  9 01:05:43 eola postfix/smtpd[31453]: disconnect from unknown[114.99.0.221] ehlo=1 auth=0/1 commands=1/2
Nov  9 01:05:43 eola postfix/smtpd[31453]: connect from unknown[114.99.0.221]
Nov  9 01:05:44 eola postfix/smtpd[31453]: lost connection after AUTH from unknown[114.99.0.221]
Nov  9 01:05:44 eola postfix/smtpd[31453]: disconnect from unknown[114.99.0.221] ehlo=1 auth=0/1 commands=1/2
Nov  9 01:05:44 eola........
-------------------------------
2019-11-09 17:59:40
114.99.0.39 attackbotsspam
Oct  1 04:33:59 mxgate1 postfix/postscreen[15902]: CONNECT from [114.99.0.39]:51190 to [176.31.12.44]:25
Oct  1 04:33:59 mxgate1 postfix/dnsblog[15906]: addr 114.99.0.39 listed by domain zen.spamhaus.org as 127.0.0.11
Oct  1 04:33:59 mxgate1 postfix/dnsblog[15906]: addr 114.99.0.39 listed by domain zen.spamhaus.org as 127.0.0.4
Oct  1 04:33:59 mxgate1 postfix/dnsblog[15904]: addr 114.99.0.39 listed by domain b.barracudacentral.org as 127.0.0.2
Oct  1 04:34:00 mxgate1 postfix/dnsblog[15907]: addr 114.99.0.39 listed by domain cbl.abuseat.org as 127.0.0.2
Oct  1 04:34:05 mxgate1 postfix/postscreen[15902]: DNSBL rank 4 for [114.99.0.39]:51190
Oct x@x
Oct  1 04:34:06 mxgate1 postfix/postscreen[15902]: DISCONNECT [114.99.0.39]:51190


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=114.99.0.39
2019-10-04 14:58:59
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.99.0.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50527
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.99.0.0.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jun 20 16:38:24 CST 2023
;; MSG SIZE  rcvd: 103
Host info
Host 0.0.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 0.0.99.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
192.241.229.85 attackspam
Port scan(s) denied
2020-05-02 00:45:55
195.231.0.89 attack
2020-05-01T15:27:07.658710abusebot-3.cloudsearch.cf sshd[11126]: Invalid user rahul from 195.231.0.89 port 53218
2020-05-01T15:27:07.664563abusebot-3.cloudsearch.cf sshd[11126]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.231.0.89
2020-05-01T15:27:07.658710abusebot-3.cloudsearch.cf sshd[11126]: Invalid user rahul from 195.231.0.89 port 53218
2020-05-01T15:27:09.629541abusebot-3.cloudsearch.cf sshd[11126]: Failed password for invalid user rahul from 195.231.0.89 port 53218 ssh2
2020-05-01T15:32:25.801024abusebot-3.cloudsearch.cf sshd[11391]: Invalid user bos from 195.231.0.89 port 37730
2020-05-01T15:32:25.809677abusebot-3.cloudsearch.cf sshd[11391]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.231.0.89
2020-05-01T15:32:25.801024abusebot-3.cloudsearch.cf sshd[11391]: Invalid user bos from 195.231.0.89 port 37730
2020-05-01T15:32:28.100207abusebot-3.cloudsearch.cf sshd[11391]: Failed password f
...
2020-05-02 00:05:00
142.93.251.1 attackspam
prod6
...
2020-05-02 00:12:54
220.172.229.87 attackspam
Telnet/23 MH Probe, Scan, BF, Hack -
2020-05-02 00:14:13
40.101.12.2 attackbots
[DoS attack: ACK Scan] (1) attack packets in last 20 sec
2020-05-02 00:10:19
89.42.252.124 attack
2020-05-01T10:39:08.4330841495-001 sshd[24335]: Invalid user mcc from 89.42.252.124 port 29203
2020-05-01T10:39:10.1696021495-001 sshd[24335]: Failed password for invalid user mcc from 89.42.252.124 port 29203 ssh2
2020-05-01T10:45:37.9652551495-001 sshd[24596]: Invalid user abc1 from 89.42.252.124 port 29203
2020-05-01T10:45:37.9725921495-001 sshd[24596]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.42.252.124
2020-05-01T10:45:37.9652551495-001 sshd[24596]: Invalid user abc1 from 89.42.252.124 port 29203
2020-05-01T10:45:39.7722611495-001 sshd[24596]: Failed password for invalid user abc1 from 89.42.252.124 port 29203 ssh2
...
2020-05-02 00:07:17
124.93.160.173 attack
2020-05-01T13:48:04.3033691240 sshd\[13421\]: Invalid user server from 124.93.160.173 port 55765
2020-05-01T13:48:04.3062461240 sshd\[13421\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.93.160.173
2020-05-01T13:48:05.9665561240 sshd\[13421\]: Failed password for invalid user server from 124.93.160.173 port 55765 ssh2
...
2020-05-02 00:22:00
66.70.130.153 attackbotsspam
May  1 17:38:35 gw1 sshd[6194]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.130.153
May  1 17:38:37 gw1 sshd[6194]: Failed password for invalid user gn from 66.70.130.153 port 47402 ssh2
...
2020-05-02 00:16:50
162.243.143.139 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-05-02 00:43:40
110.232.65.83 attackbotsspam
SSH Brute-Forcing (server2)
2020-05-02 00:44:58
152.136.105.190 attack
2020-05-01T15:58:59.342141shield sshd\[27830\]: Invalid user bob from 152.136.105.190 port 41044
2020-05-01T15:58:59.346063shield sshd\[27830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.105.190
2020-05-01T15:59:00.469873shield sshd\[27830\]: Failed password for invalid user bob from 152.136.105.190 port 41044 ssh2
2020-05-01T16:03:00.971902shield sshd\[28305\]: Invalid user paci from 152.136.105.190 port 56362
2020-05-01T16:03:00.975486shield sshd\[28305\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.105.190
2020-05-02 00:08:53
123.11.174.76 attack
Telnet/23 MH Probe, Scan, BF, Hack -
2020-05-02 00:44:10
162.243.139.146 attack
scans once in preceeding hours on the ports (in chronological order) 2323 resulting in total of 94 scans from 162.243.0.0/16 block.
2020-05-02 00:32:02
141.98.9.157 attackspambots
5x Failed Password
2020-05-02 00:15:09
51.178.78.154 attackbots
Excessive Port-Scanning
2020-05-02 00:33:51

Recently Reported IPs

78.46.214.6 222.211.249.231 148.9.164.135 231.71.87.61
176.58.106.79 213.136.71.218 79.195.20.157 111.90.159.182
0.18.28.179 193.19.207.170 138.70.68.63 108.252.38.107
185.122.41.213 108.181.33.59 182.67.164.148 163.172.52.115
47.242.113.187 56.107.116.47 128.86.223.236 72.72.197.34