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

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

;; QUESTION SECTION:
;104.144.50.195.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 16:02:12 CST 2022
;; MSG SIZE  rcvd: 107
Host info
195.50.144.104.in-addr.arpa domain name pointer 3f2092.expling.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
195.50.144.104.in-addr.arpa	name = 3f2092.expling.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
177.84.222.24 attack
2019-08-09T23:08:45.036444abusebot-7.cloudsearch.cf sshd\[17309\]: Invalid user qa from 177.84.222.24 port 43937
2019-08-10 07:36:40
181.40.66.136 attackbotsspam
Unauthorized connection attempt from IP address 181.40.66.136 on Port 445(SMB)
2019-08-10 07:04:18
132.232.45.138 attack
Brute force SMTP login attempted.
...
2019-08-10 07:29:55
159.89.163.235 attackbots
Aug  9 18:51:06 ny01 sshd[23710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.163.235
Aug  9 18:51:07 ny01 sshd[23710]: Failed password for invalid user administrador from 159.89.163.235 port 46300 ssh2
Aug  9 18:55:59 ny01 sshd[24096]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.163.235
2019-08-10 07:02:03
132.247.16.76 attack
ssh failed login
2019-08-10 07:22:16
132.232.64.124 attackspam
Brute force SMTP login attempted.
...
2019-08-10 07:26:48
133.130.89.210 attackbots
SSH authentication failure x 6 reported by Fail2Ban
...
2019-08-10 07:08:05
132.232.33.161 attack
Brute force SMTP login attempted.
...
2019-08-10 07:33:37
111.230.228.183 attackspam
SSHScan
2019-08-10 07:15:50
117.191.67.213 attack
Invalid user be from 117.191.67.213 port 31972
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.191.67.213
Failed password for invalid user be from 117.191.67.213 port 31972 ssh2
Invalid user sql from 117.191.67.213 port 49724
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.191.67.213
2019-08-10 07:19:17
187.102.61.54 attackbotsspam
Automatic report - Port Scan Attack
2019-08-10 07:31:04
165.22.248.163 attackbotsspam
SpamReport
2019-08-10 07:14:22
132.232.80.107 attack
Brute force SMTP login attempted.
...
2019-08-10 07:25:28
132.232.43.115 attack
Brute force SMTP login attempted.
...
2019-08-10 07:31:32
113.200.88.211 attack
what?
2019-08-10 07:36:30

Recently Reported IPs

104.144.50.178 104.144.50.191 104.144.50.215 104.144.50.193
104.144.50.104 104.144.50.29 104.144.50.222 104.144.50.235
104.144.50.77 104.144.50.30 104.144.50.95 104.144.50.78
104.144.50.45 104.144.50.39 104.144.51.102 104.144.51.100
104.144.51.105 104.144.51.11 104.144.51.12 104.144.51.111