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

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

;; QUESTION SECTION:
;104.85.119.41.			IN	A

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

;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:32:49 CST 2023
;; MSG SIZE  rcvd: 106
Host info
41.119.85.104.in-addr.arpa domain name pointer a104-85-119-41.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
41.119.85.104.in-addr.arpa	name = a104-85-119-41.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
78.131.11.10 attack
SSH bruteforce
2020-02-18 03:03:47
61.19.22.217 attack
Feb 17 19:42:44 MK-Soft-VM8 sshd[22869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.19.22.217 
Feb 17 19:42:46 MK-Soft-VM8 sshd[22869]: Failed password for invalid user eugen from 61.19.22.217 port 49976 ssh2
...
2020-02-18 03:26:31
37.187.117.187 attackspam
Feb 17 19:55:17 pornomens sshd\[24520\]: Invalid user debian from 37.187.117.187 port 44056
Feb 17 19:55:17 pornomens sshd\[24520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.117.187
Feb 17 19:55:20 pornomens sshd\[24520\]: Failed password for invalid user debian from 37.187.117.187 port 44056 ssh2
...
2020-02-18 03:11:41
37.114.164.217 attack
Brute force attempt
2020-02-18 03:18:35
14.229.63.172 attack
Automatic report - Port Scan Attack
2020-02-18 03:31:31
113.23.43.77 attackbotsspam
20/2/17@08:34:34: FAIL: Alarm-Network address from=113.23.43.77
...
2020-02-18 03:24:46
129.211.121.171 attackspambots
Feb 17 17:13:17 sd-53420 sshd\[8007\]: Invalid user spread from 129.211.121.171
Feb 17 17:13:17 sd-53420 sshd\[8007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.121.171
Feb 17 17:13:19 sd-53420 sshd\[8007\]: Failed password for invalid user spread from 129.211.121.171 port 38276 ssh2
Feb 17 17:16:43 sd-53420 sshd\[8361\]: Invalid user server from 129.211.121.171
Feb 17 17:16:43 sd-53420 sshd\[8361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.121.171
...
2020-02-18 03:36:29
163.172.53.162 attackspam
Unauthorized connection attempt detected from IP address 163.172.53.162 to port 139
2020-02-18 03:37:05
113.172.66.47 attackspambots
"SMTP brute force auth login attempt."
2020-02-18 03:07:08
223.16.186.102 attack
Port probing on unauthorized port 5555
2020-02-18 03:23:42
222.186.15.166 attackspambots
$f2bV_matches
2020-02-18 03:38:25
49.228.136.188 attack
Brute-force general attack.
2020-02-18 03:17:59
138.99.79.231 attackspam
Automatic report - Port Scan Attack
2020-02-18 03:17:45
92.63.194.15 attack
(RDP) trying to logon to a computer they shouldn't be
2020-02-18 03:29:33
111.230.110.87 attackspambots
" "
2020-02-18 03:00:45

Recently Reported IPs

104.84.252.11 104.84.79.58 104.85.101.134 104.84.85.207
104.84.55.30 104.84.154.53 104.85.113.248 104.85.130.37
104.84.59.204 104.84.48.13 104.84.83.93 104.85.161.76
104.84.66.9 104.85.169.152 104.84.70.13 104.85.175.234
104.85.147.179 104.85.180.37 104.84.238.255 104.85.10.25