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:
IP Type Details Datetime
114.99.22.89 attack
Lines containing failures of 114.99.22.89


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=114.99.22.89
2020-04-02 17:18:58
114.99.225.109 attackbotsspam
Mar 20 04:49:16 zimbra postfix/smtps/smtpd[21345]: lost connection after CONNECT from unknown[114.99.225.109]
Mar 20 04:50:25 zimbra postfix/smtps/smtpd[21346]: warning: unknown[114.99.225.109]: SASL LOGIN authentication failed: authentication failure
Mar 20 04:50:26 zimbra postfix/smtps/smtpd[21346]: lost connection after AUTH from unknown[114.99.225.109]
Mar 20 04:50:26 zimbra postfix/smtps/smtpd[21346]: disconnect from unknown[114.99.225.109] ehlo=1 auth=0/1 commands=1/2
...
2020-03-20 20:13:18
114.99.22.143 attackbots
Unauthorized connection attempt detected from IP address 114.99.22.143 to port 6656 [T]
2020-01-30 15:18:25
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.99.22.104
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5003
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.99.22.104.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 03:44:26 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 104.22.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 104.22.99.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
188.163.83.173 attackbotsspam
Automatic report - Port Scan Attack
2019-07-24 13:50:53
209.97.182.100 attack
Jul 24 07:31:28 giegler sshd[5037]: Invalid user traffic from 209.97.182.100 port 54228
2019-07-24 13:42:49
51.91.36.96 attackspam
Invalid user zabbix from 51.91.36.96 port 60326
2019-07-24 13:28:26
14.98.4.82 attack
Jul 24 07:26:32 meumeu sshd[30476]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.98.4.82 
Jul 24 07:26:34 meumeu sshd[30476]: Failed password for invalid user test2 from 14.98.4.82 port 40604 ssh2
Jul 24 07:31:47 meumeu sshd[6637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.98.4.82 
...
2019-07-24 13:47:46
106.52.68.193 attackspam
HTTP/80/443 Probe, Hack -
2019-07-24 12:58:06
92.53.65.136 attack
Splunk® : port scan detected:
Jul 24 00:02:18 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=92.53.65.136 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x20 TTL=246 ID=63394 PROTO=TCP SPT=44533 DPT=4121 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-24 12:53:35
173.44.34.84 attackbotsspam
19/7/23@16:06:22: FAIL: Alarm-Intrusion address from=173.44.34.84
...
2019-07-24 13:14:16
91.134.242.199 attackspam
Jul 24 06:49:16 SilenceServices sshd[4157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.242.199
Jul 24 06:49:19 SilenceServices sshd[4157]: Failed password for invalid user olimex from 91.134.242.199 port 49682 ssh2
Jul 24 06:53:31 SilenceServices sshd[7358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.242.199
2019-07-24 13:09:00
202.104.29.14 attack
Automatic report - Port Scan Attack
2019-07-24 13:49:47
54.37.151.239 attackbotsspam
Jul 24 07:24:40 SilenceServices sshd[30004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.151.239
Jul 24 07:24:42 SilenceServices sshd[30004]: Failed password for invalid user fog from 54.37.151.239 port 52054 ssh2
Jul 24 07:30:29 SilenceServices sshd[1615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.151.239
2019-07-24 13:41:57
100.37.96.138 attackspam
Jul 23 19:56:10 localhost sshd\[20916\]: Invalid user testuser from 100.37.96.138 port 12858
Jul 23 19:56:10 localhost sshd\[20916\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=100.37.96.138
Jul 23 19:56:12 localhost sshd\[20916\]: Failed password for invalid user testuser from 100.37.96.138 port 12858 ssh2
Jul 23 20:06:58 localhost sshd\[21253\]: Invalid user lambda from 100.37.96.138 port 13389
Jul 23 20:06:58 localhost sshd\[21253\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=100.37.96.138
...
2019-07-24 12:58:39
174.136.12.73 attackspam
Probing for vulnerable PHP code /wp-includes/Requests/Exception/HTTP/sbrjoqph.php
2019-07-24 13:09:23
138.68.146.186 attack
Invalid user administrateur from 138.68.146.186 port 56056
2019-07-24 13:02:54
218.92.0.197 attack
Jul 23 22:06:43 ArkNodeAT sshd\[23976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.197  user=root
Jul 23 22:06:45 ArkNodeAT sshd\[23976\]: Failed password for root from 218.92.0.197 port 63633 ssh2
Jul 23 22:06:48 ArkNodeAT sshd\[23976\]: Failed password for root from 218.92.0.197 port 63633 ssh2
2019-07-24 13:00:56
54.36.64.245 attackbots
WordPress wp-login brute force :: 54.36.64.245 0.068 BYPASS [24/Jul/2019:14:41:05  1000] [censored_4] "POST /wp-login.php HTTP/1.1" 200 4214 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-24 12:51:49

Recently Reported IPs

114.99.21.96 114.99.22.100 114.99.21.98 114.99.22.102
115.237.81.198 114.99.22.106 114.99.22.110 114.99.22.117
114.99.22.11 114.99.22.114 114.99.22.12 114.99.22.112
114.99.22.118 114.99.22.127 114.99.22.120 114.99.22.124
115.237.81.204 114.99.22.122 114.99.22.128 114.99.22.130