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:
IP Type Details Datetime
172.104.92.168 attackbots
scans once in preceeding hours on the ports (in chronological order) 4567 resulting in total of 2 scans from 172.104.0.0/15 block.
2020-08-27 00:13:26
172.104.92.168 attackbots
firewall-block, port(s): 4567/tcp
2020-07-20 22:18:34
172.104.92.168 attack
 TCP (SYN) 172.104.92.168:45258 -> port 4567, len 44
2020-06-14 23:50:32
172.104.92.168 attackspambots
Port Scan detected!
...
2020-05-24 23:14:30
172.104.92.209 attackspam
scans once in preceeding hours on the ports (in chronological order) 1900 resulting in total of 4 scans from 172.104.0.0/15 block.
2020-04-25 22:32:33
172.104.92.209 attackbotsspam
1900/tcp 1900/tcp 1900/tcp...
[2020-01-31/04-01]74pkt,1pt.(tcp)
2020-04-01 20:39:51
172.104.92.168 attackbots
firewall-block, port(s): 4567/tcp
2020-03-07 07:26:16
172.104.92.168 attackbots
firewall-block, port(s): 4567/tcp
2020-02-29 00:49:14
172.104.92.209 attackbotsspam
unauthorized connection attempt
2020-02-19 13:28:11
172.104.92.166 attack
Unauthorized connection attempt detected from IP address 172.104.92.166 to port 8000
2020-02-12 02:26:51
172.104.92.168 attackspam
trying to access non-authorized port
2020-02-11 15:18:00
172.104.92.209 attackspambots
" "
2020-02-10 05:20:28
172.104.92.209 attack
firewall-block, port(s): 1900/tcp
2020-02-05 21:53:17
172.104.92.209 attack
1900/tcp 1900/tcp 1900/tcp...
[2019-11-28/2020-01-26]74pkt,1pt.(tcp)
2020-01-28 02:55:25
172.104.92.168 attack
Jan 27 10:50:05 debian-2gb-nbg1-2 kernel: \[2377874.376361\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=172.104.92.168 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=57366 DPT=4567 WINDOW=65535 RES=0x00 SYN URGP=0
2020-01-28 01:10:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 172.104.92.220
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45619
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;172.104.92.220.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 15:13:53 CST 2022
;; MSG SIZE  rcvd: 107
Host info
220.92.104.172.in-addr.arpa domain name pointer li1702-220.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
220.92.104.172.in-addr.arpa	name = li1702-220.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.116.35.144 attack
2020-05-08T04:55:59.622012server.espacesoutien.com sshd[18246]: Failed password for root from 45.116.35.144 port 39162 ssh2
2020-05-08T04:57:09.670553server.espacesoutien.com sshd[18367]: Invalid user import from 45.116.35.144 port 54654
2020-05-08T04:57:09.685362server.espacesoutien.com sshd[18367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.116.35.144
2020-05-08T04:57:09.670553server.espacesoutien.com sshd[18367]: Invalid user import from 45.116.35.144 port 54654
2020-05-08T04:57:11.484798server.espacesoutien.com sshd[18367]: Failed password for invalid user import from 45.116.35.144 port 54654 ssh2
...
2020-05-08 19:52:24
164.160.22.159 attackbots
Automatic report - Port Scan Attack
2020-05-08 19:51:42
164.138.23.149 attackspam
May  8 06:14:09 inter-technics sshd[6870]: Invalid user nils from 164.138.23.149 port 37391
May  8 06:14:09 inter-technics sshd[6870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.138.23.149
May  8 06:14:09 inter-technics sshd[6870]: Invalid user nils from 164.138.23.149 port 37391
May  8 06:14:11 inter-technics sshd[6870]: Failed password for invalid user nils from 164.138.23.149 port 37391 ssh2
May  8 06:17:40 inter-technics sshd[7199]: Invalid user wcj from 164.138.23.149 port 37269
...
2020-05-08 19:58:10
195.60.191.65 attack
port 23
2020-05-08 19:39:29
186.10.102.182 attack
Unauthorized connection attempt from IP address 186.10.102.182 on Port 445(SMB)
2020-05-08 20:21:06
47.241.7.235 attackspam
bruteforce detected
2020-05-08 20:13:28
185.220.100.253 attackspam
May  8 13:42:35 vmd48417 sshd[30020]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.100.253
2020-05-08 20:16:27
202.168.71.146 attackspam
2020-05-08T13:09:27.7598831240 sshd\[31825\]: Invalid user deploy from 202.168.71.146 port 56756
2020-05-08T13:09:27.7637121240 sshd\[31825\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.168.71.146
2020-05-08T13:09:30.1829001240 sshd\[31825\]: Failed password for invalid user deploy from 202.168.71.146 port 56756 ssh2
...
2020-05-08 20:03:13
112.85.42.89 attack
May  8 13:50:09 ns381471 sshd[11687]: Failed password for root from 112.85.42.89 port 30570 ssh2
2020-05-08 20:10:53
51.210.15.5 attackspam
2020-05-08T06:15:58.155500linuxbox-skyline sshd[21828]: Invalid user bob from 51.210.15.5 port 35476
...
2020-05-08 20:20:46
188.166.150.17 attackbots
May  8 08:04:56 pkdns2 sshd\[42458\]: Invalid user oem from 188.166.150.17May  8 08:04:58 pkdns2 sshd\[42458\]: Failed password for invalid user oem from 188.166.150.17 port 49932 ssh2May  8 08:08:29 pkdns2 sshd\[42691\]: Invalid user csgoserver from 188.166.150.17May  8 08:08:30 pkdns2 sshd\[42691\]: Failed password for invalid user csgoserver from 188.166.150.17 port 54334 ssh2May  8 08:12:07 pkdns2 sshd\[42869\]: Invalid user christian from 188.166.150.17May  8 08:12:08 pkdns2 sshd\[42869\]: Failed password for invalid user christian from 188.166.150.17 port 58723 ssh2
...
2020-05-08 20:07:09
94.25.224.93 attackspambots
Unauthorized connection attempt from IP address 94.25.224.93 on Port 445(SMB)
2020-05-08 20:18:47
14.116.255.229 attackspambots
May  8 08:22:43 ns3033917 sshd[9167]: Invalid user webserver from 14.116.255.229 port 35420
May  8 08:22:45 ns3033917 sshd[9167]: Failed password for invalid user webserver from 14.116.255.229 port 35420 ssh2
May  8 08:33:33 ns3033917 sshd[9235]: Invalid user lobby from 14.116.255.229 port 43770
...
2020-05-08 19:41:15
122.225.230.10 attackspam
2020-05-08T12:08:18.220831shield sshd\[6974\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.225.230.10  user=root
2020-05-08T12:08:20.383659shield sshd\[6974\]: Failed password for root from 122.225.230.10 port 40588 ssh2
2020-05-08T12:12:06.038653shield sshd\[7584\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.225.230.10  user=root
2020-05-08T12:12:08.501935shield sshd\[7584\]: Failed password for root from 122.225.230.10 port 46868 ssh2
2020-05-08T12:15:57.769117shield sshd\[8069\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.225.230.10  user=root
2020-05-08 20:22:33
49.72.51.199 attack
20 attempts against mh-ssh on cloud
2020-05-08 19:48:06

Recently Reported IPs

172.104.99.133 172.104.99.206 172.105.0.118 172.105.102.101
172.105.103.214 172.105.104.112 172.105.104.155 172.105.104.140
172.105.105.209 172.105.105.44 172.105.107.51 172.105.11.160
172.105.112.43 172.105.113.58 172.105.112.55 172.105.115.113
172.105.106.80 172.105.115.55 172.105.117.173 172.105.119.197