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

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;116.91.189.20.			IN	A

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

;; Query time: 118 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 16 23:39:16 CST 2019
;; MSG SIZE  rcvd: 117
Host info
20.189.91.116.in-addr.arpa domain name pointer 116-91-189-20.tokyo.ap.gmo-isp.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
20.189.91.116.in-addr.arpa	name = 116-91-189-20.tokyo.ap.gmo-isp.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
64.34.30.163 attackspam
Invalid user tstuser from 64.34.30.163 port 60028
2019-10-27 04:28:15
202.29.220.186 attackbots
Oct 26 22:29:35 tor-proxy-08 sshd\[4913\]: Invalid user pi from 202.29.220.186 port 56850
Oct 26 22:29:35 tor-proxy-08 sshd\[4914\]: Invalid user pi from 202.29.220.186 port 56852
Oct 26 22:29:35 tor-proxy-08 sshd\[4913\]: Connection closed by 202.29.220.186 port 56850 \[preauth\]
Oct 26 22:29:36 tor-proxy-08 sshd\[4914\]: Connection closed by 202.29.220.186 port 56852 \[preauth\]
...
2019-10-27 04:35:12
112.85.42.87 attackbotsspam
2019-10-26T20:50:35.479085shield sshd\[4200\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.87  user=root
2019-10-26T20:50:37.369502shield sshd\[4200\]: Failed password for root from 112.85.42.87 port 21187 ssh2
2019-10-26T20:50:39.795214shield sshd\[4200\]: Failed password for root from 112.85.42.87 port 21187 ssh2
2019-10-26T20:50:41.967635shield sshd\[4200\]: Failed password for root from 112.85.42.87 port 21187 ssh2
2019-10-26T20:52:10.954911shield sshd\[4765\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.87  user=root
2019-10-27 05:02:47
189.85.84.86 attackbots
Automatic report - Banned IP Access
2019-10-27 04:47:05
51.91.36.28 attack
Oct 26 23:24:32 sauna sshd[9741]: Failed password for root from 51.91.36.28 port 55782 ssh2
...
2019-10-27 04:34:24
86.57.217.241 attackbotsspam
2019-10-26T20:29:38.190872abusebot.cloudsearch.cf sshd\[26908\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.57.217.241  user=root
2019-10-27 04:34:40
66.249.79.25 attack
Automatic report - Banned IP Access
2019-10-27 05:01:24
218.246.5.117 attackspambots
Oct 26 22:29:40 dedicated sshd[19220]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.246.5.117  user=root
Oct 26 22:29:41 dedicated sshd[19220]: Failed password for root from 218.246.5.117 port 46304 ssh2
2019-10-27 04:32:10
159.203.198.34 attack
Oct 26 10:30:24 hanapaa sshd\[4372\]: Invalid user maria from 159.203.198.34
Oct 26 10:30:24 hanapaa sshd\[4372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.198.34
Oct 26 10:30:26 hanapaa sshd\[4372\]: Failed password for invalid user maria from 159.203.198.34 port 39927 ssh2
Oct 26 10:37:32 hanapaa sshd\[4960\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.198.34  user=root
Oct 26 10:37:33 hanapaa sshd\[4960\]: Failed password for root from 159.203.198.34 port 38630 ssh2
2019-10-27 04:45:52
61.41.159.29 attackbotsspam
Invalid user applmgr from 61.41.159.29 port 50304
2019-10-27 04:28:28
60.249.188.118 attackbotsspam
Oct 26 20:54:49 hcbbdb sshd\[18133\]: Invalid user wasadrc from 60.249.188.118
Oct 26 20:54:49 hcbbdb sshd\[18133\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60-249-188-118.hinet-ip.hinet.net
Oct 26 20:54:52 hcbbdb sshd\[18133\]: Failed password for invalid user wasadrc from 60.249.188.118 port 50806 ssh2
Oct 26 20:58:36 hcbbdb sshd\[18524\]: Invalid user bounce from 60.249.188.118
Oct 26 20:58:36 hcbbdb sshd\[18524\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60-249-188-118.hinet-ip.hinet.net
2019-10-27 05:02:01
172.81.212.111 attackspam
Oct 26 22:25:03 SilenceServices sshd[8687]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.212.111
Oct 26 22:25:05 SilenceServices sshd[8687]: Failed password for invalid user win*2012 from 172.81.212.111 port 58734 ssh2
Oct 26 22:29:18 SilenceServices sshd[11384]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.212.111
2019-10-27 04:44:44
192.186.188.143 attackbotsspam
Chat Spam
2019-10-27 04:37:24
5.39.77.117 attackspambots
Invalid user user from 5.39.77.117 port 55341
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.77.117
Failed password for invalid user user from 5.39.77.117 port 55341 ssh2
Invalid user nt from 5.39.77.117 port 46408
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.77.117
2019-10-27 04:30:31
122.165.155.19 attackbots
Oct 27 01:53:38 areeb-Workstation sshd[414]: Failed password for root from 122.165.155.19 port 35582 ssh2
...
2019-10-27 04:48:02

Recently Reported IPs

195.217.211.95 200.159.225.79 61.206.3.37 8.39.183.146
103.109.166.101 92.38.173.10 120.249.163.41 49.63.14.80
123.25.56.240 103.125.190.245 40.92.71.95 58.52.49.235
40.92.65.92 18.220.84.93 216.37.177.20 14.226.188.2
14.98.106.58 103.207.131.203 94.176.237.208 82.112.185.205