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: United States

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

;; QUESTION SECTION:
;214.136.86.89.			IN	A

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

;; Query time: 89 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 03 19:07:10 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 89.86.136.214.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 214.136.86.89.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
113.108.126.21 attackbots
21/tcp 21/tcp 21/tcp
[2019-11-21]3pkt
2019-11-21 16:09:19
27.50.24.83 attackbots
Nov 21 08:38:33 tuxlinux sshd[5154]: Invalid user manager from 27.50.24.83 port 9224
Nov 21 08:38:33 tuxlinux sshd[5154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.50.24.83 
Nov 21 08:38:33 tuxlinux sshd[5154]: Invalid user manager from 27.50.24.83 port 9224
Nov 21 08:38:33 tuxlinux sshd[5154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.50.24.83 
Nov 21 08:38:33 tuxlinux sshd[5154]: Invalid user manager from 27.50.24.83 port 9224
Nov 21 08:38:33 tuxlinux sshd[5154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.50.24.83 
Nov 21 08:38:35 tuxlinux sshd[5154]: Failed password for invalid user manager from 27.50.24.83 port 9224 ssh2
...
2019-11-21 15:58:06
61.2.192.16 attackspam
Unauthorised access (Nov 21) SRC=61.2.192.16 LEN=52 PREC=0x20 TTL=110 ID=22875 DF TCP DPT=1433 WINDOW=8192 SYN
2019-11-21 16:19:04
167.71.223.191 attack
Nov 21 09:01:34 sd-53420 sshd\[28951\]: User www-data from 167.71.223.191 not allowed because none of user's groups are listed in AllowGroups
Nov 21 09:01:34 sd-53420 sshd\[28951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.223.191  user=www-data
Nov 21 09:01:37 sd-53420 sshd\[28951\]: Failed password for invalid user www-data from 167.71.223.191 port 37578 ssh2
Nov 21 09:05:40 sd-53420 sshd\[30298\]: User root from 167.71.223.191 not allowed because none of user's groups are listed in AllowGroups
Nov 21 09:05:40 sd-53420 sshd\[30298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.223.191  user=root
...
2019-11-21 16:09:55
23.129.64.203 attack
detected by Fail2Ban
2019-11-21 16:19:57
63.88.23.250 attack
63.88.23.250 was recorded 9 times by 7 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 9, 89, 464
2019-11-21 16:18:38
94.23.208.211 attackbots
Nov 21 09:37:50 server sshd\[24460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns303460.ip-94-23-208.eu  user=apache
Nov 21 09:37:52 server sshd\[24460\]: Failed password for apache from 94.23.208.211 port 60140 ssh2
Nov 21 09:52:39 server sshd\[28039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns303460.ip-94-23-208.eu  user=root
Nov 21 09:52:40 server sshd\[28039\]: Failed password for root from 94.23.208.211 port 42914 ssh2
Nov 21 09:55:54 server sshd\[28992\]: Invalid user ching from 94.23.208.211
Nov 21 09:55:54 server sshd\[28992\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns303460.ip-94-23-208.eu 
...
2019-11-21 16:20:12
106.75.15.142 attackbotsspam
Nov 21 09:29:00 MK-Soft-Root2 sshd[32660]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.15.142 
Nov 21 09:29:02 MK-Soft-Root2 sshd[32660]: Failed password for invalid user world from 106.75.15.142 port 51678 ssh2
...
2019-11-21 16:37:01
114.79.160.36 attack
" "
2019-11-21 16:34:03
111.68.97.59 attackspam
Automatic report - Banned IP Access
2019-11-21 16:34:24
185.120.221.215 attackbotsspam
C1,WP GET /nelson/wp-login.php
2019-11-21 16:06:00
116.111.183.67 attackbotsspam
Nov 19 11:49:29 mxgate1 postfix/postscreen[659]: CONNECT from [116.111.183.67]:13818 to [176.31.12.44]:25
Nov 19 11:49:29 mxgate1 postfix/dnsblog[666]: addr 116.111.183.67 listed by domain zen.spamhaus.org as 127.0.0.11
Nov 19 11:49:29 mxgate1 postfix/dnsblog[666]: addr 116.111.183.67 listed by domain zen.spamhaus.org as 127.0.0.3
Nov 19 11:49:29 mxgate1 postfix/dnsblog[666]: addr 116.111.183.67 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 19 11:49:29 mxgate1 postfix/dnsblog[667]: addr 116.111.183.67 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 19 11:49:29 mxgate1 postfix/dnsblog[665]: addr 116.111.183.67 listed by domain b.barracudacentral.org as 127.0.0.2
Nov 19 11:49:35 mxgate1 postfix/postscreen[659]: DNSBL rank 4 for [116.111.183.67]:13818
Nov x@x
Nov 19 11:49:36 mxgate1 postfix/postscreen[659]: HANGUP after 1 from [116.111.183.67]:13818 in tests after SMTP handshake
Nov 19 11:49:36 mxgate1 postfix/postscreen[659]: DISCONNECT [116.111.183.67]:13818


........
----------------------------------
2019-11-21 16:19:34
119.29.15.120 attackspam
Nov 21 02:55:22 TORMINT sshd\[14723\]: Invalid user host from 119.29.15.120
Nov 21 02:55:22 TORMINT sshd\[14723\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.15.120
Nov 21 02:55:24 TORMINT sshd\[14723\]: Failed password for invalid user host from 119.29.15.120 port 58877 ssh2
...
2019-11-21 16:03:57
192.99.244.119 attack
Nov 19 10:45:27 mxgate1 postfix/postscreen[30543]: CONNECT from [192.99.244.119]:39253 to [176.31.12.44]:25
Nov 19 10:45:27 mxgate1 postfix/dnsblog[30544]: addr 192.99.244.119 listed by domain zen.spamhaus.org as 127.0.0.3
Nov 19 10:45:33 mxgate1 postfix/postscreen[30543]: DNSBL rank 2 for [192.99.244.119]:39253
Nov 19 10:45:33 mxgate1 postfix/tlsproxy[30887]: CONNECT from [192.99.244.119]:39253
Nov x@x
Nov 19 10:45:34 mxgate1 postfix/postscreen[30543]: DISCONNECT [192.99.244.119]:39253
Nov 19 10:45:34 mxgate1 postfix/tlsproxy[30887]: DISCONNECT [192.99.244.119]:39253


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=192.99.244.119
2019-11-21 16:04:22
36.230.183.5 attack
Honeypot attack, port: 23, PTR: 36-230-183-5.dynamic-ip.hinet.net.
2019-11-21 16:32:51

Recently Reported IPs

208.60.200.159 136.97.116.49 251.198.218.20 154.140.136.243
0.9.91.54 237.21.174.76 182.34.200.193 79.159.36.39
24.23.128.227 43.251.236.171 221.212.127.62 192.25.178.98
243.153.247.252 105.128.114.31 96.34.138.162 71.46.223.120
180.82.207.79 142.32.165.96 152.162.133.17 167.251.166.95