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 of America

Internet Service Provider: ColoCrossing

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbotsspam
2020-06-23T05:51:38.637285struts4.enskede.local sshd\[23308\]: Invalid user fake from 192.3.104.106 port 39572
2020-06-23T05:51:38.648668struts4.enskede.local sshd\[23308\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.104.106
2020-06-23T05:51:41.709698struts4.enskede.local sshd\[23308\]: Failed password for invalid user fake from 192.3.104.106 port 39572 ssh2
2020-06-23T05:51:42.861524struts4.enskede.local sshd\[23310\]: Invalid user ubnt from 192.3.104.106 port 42926
2020-06-23T05:51:42.870192struts4.enskede.local sshd\[23310\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.104.106
...
2020-06-23 17:25:29
attackbotsspam
Invalid user fake from 192.3.104.106 port 33042
2020-06-18 06:23:53
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.3.104.106
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56514
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 47 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 18 06:23:46 CST 2020
;; MSG SIZE  rcvd: 117
Host info
106.104.3.192.in-addr.arpa domain name pointer 192-3-104-106-host.colocrossing.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
106.104.3.192.in-addr.arpa	name = 192-3-104-106-host.colocrossing.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
187.51.12.106 attackspam
Jul  9 14:09:10 debian-2gb-nbg1-2 kernel: \[16555144.777430\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=187.51.12.106 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=236 ID=45776 PROTO=TCP SPT=45781 DPT=26623 WINDOW=1024 RES=0x00 SYN URGP=0
2020-07-09 21:01:43
192.241.235.22 attackbotsspam
TCP port 3389: Scan and connection
2020-07-09 21:01:28
164.68.112.178 attackspambots
 TCP (SYN) 164.68.112.178:53025 -> port 16993, len 44
2020-07-09 20:45:04
183.82.121.34 attack
$f2bV_matches
2020-07-09 20:34:15
61.177.172.168 attack
Jul  9 14:37:30 home sshd[5775]: Failed password for root from 61.177.172.168 port 5005 ssh2
Jul  9 14:37:34 home sshd[5775]: Failed password for root from 61.177.172.168 port 5005 ssh2
Jul  9 14:37:44 home sshd[5775]: Failed password for root from 61.177.172.168 port 5005 ssh2
Jul  9 14:37:44 home sshd[5775]: error: maximum authentication attempts exceeded for root from 61.177.172.168 port 5005 ssh2 [preauth]
...
2020-07-09 20:42:04
191.235.239.168 attack
Jul  9 12:38:44 bchgang sshd[3606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.235.239.168
Jul  9 12:38:47 bchgang sshd[3606]: Failed password for invalid user radio from 191.235.239.168 port 56752 ssh2
Jul  9 12:45:35 bchgang sshd[3839]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.235.239.168
...
2020-07-09 20:59:08
78.222.93.54 attackspam
Unauthorised connection attempt detected at AUO NODE 4. System is sshd. Protected by AUO Stack Web Application Firewall (WAF)
2020-07-09 20:29:49
177.152.124.23 attackbotsspam
Jul  9 14:09:37 pve1 sshd[1670]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.152.124.23 
Jul  9 14:09:38 pve1 sshd[1670]: Failed password for invalid user geoffrey from 177.152.124.23 port 35038 ssh2
...
2020-07-09 20:24:44
185.132.249.237 attackspambots
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-07-09 20:27:41
85.242.164.206 attackbotsspam
postfix
2020-07-09 20:50:58
212.64.71.225 attackbots
Jul  9 09:06:24 firewall sshd[18515]: Invalid user zjnsh from 212.64.71.225
Jul  9 09:06:26 firewall sshd[18515]: Failed password for invalid user zjnsh from 212.64.71.225 port 46980 ssh2
Jul  9 09:09:14 firewall sshd[18590]: Invalid user wtd from 212.64.71.225
...
2020-07-09 20:58:42
46.20.34.169 attack
xmlrpc attack
2020-07-09 20:47:18
182.71.65.49 attack
20/7/9@08:09:20: FAIL: Alarm-Network address from=182.71.65.49
20/7/9@08:09:21: FAIL: Alarm-Network address from=182.71.65.49
...
2020-07-09 20:52:16
51.91.159.46 attackbotsspam
Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-07-09T11:43:32Z and 2020-07-09T12:09:25Z
2020-07-09 20:49:18
93.147.98.19 attackspam
postfix
2020-07-09 20:53:12

Recently Reported IPs

123.21.175.105 93.243.183.228 90.18.12.114 112.155.166.215
213.229.86.156 113.172.125.84 176.44.233.149 109.128.69.213
80.27.71.38 69.255.4.119 101.108.62.225 65.184.137.53
172.44.88.59 17.236.96.197 177.22.212.54 12.135.135.62
218.231.109.66 100.137.212.13 97.157.102.243 104.175.172.178