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 (the)

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

;; QUESTION SECTION:
;104.117.187.85.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 20:44:32 CST 2025
;; MSG SIZE  rcvd: 107
Host info
85.187.117.104.in-addr.arpa domain name pointer a104-117-187-85.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
85.187.117.104.in-addr.arpa	name = a104-117-187-85.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
3.88.192.210 attackspam
Fail2Ban Ban Triggered
2019-07-17 02:24:20
60.20.224.208 attack
Honeypot attack, port: 23, PTR: PTR record not found
2019-07-17 02:18:37
185.222.211.114 attack
Jul 16 19:19:29 lumpi kernel: INPUT:DROP:SPAMHAUS_DROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=185.222.211.114 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=35784 PROTO=TCP SPT=41487 DPT=3319 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-07-17 02:29:14
52.65.212.225 attack
RDP Brute-Force (Grieskirchen RZ1)
2019-07-17 02:15:43
182.61.160.15 attack
SSH Brute-Force reported by Fail2Ban
2019-07-17 02:53:28
49.83.170.1 attackspam
abuse-sasl
2019-07-17 02:37:56
157.230.146.88 attackbots
Unauthorized SSH login attempts
2019-07-17 02:55:55
79.137.35.70 attackbotsspam
Jul 16 16:40:39 ip-172-31-1-72 sshd\[24414\]: Invalid user hal from 79.137.35.70
Jul 16 16:40:39 ip-172-31-1-72 sshd\[24414\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.35.70
Jul 16 16:40:40 ip-172-31-1-72 sshd\[24414\]: Failed password for invalid user hal from 79.137.35.70 port 57164 ssh2
Jul 16 16:45:05 ip-172-31-1-72 sshd\[24482\]: Invalid user demon from 79.137.35.70
Jul 16 16:45:05 ip-172-31-1-72 sshd\[24482\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.35.70
2019-07-17 02:39:08
206.189.165.94 attack
Jul 16 15:09:30 lnxded63 sshd[26897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.165.94
2019-07-17 02:56:54
170.0.236.182 attackspambots
3389BruteforceFW22
2019-07-17 03:05:29
27.198.50.122 attack
leo_www
2019-07-17 02:44:03
185.176.27.42 attackspambots
16.07.2019 18:37:05 Connection to port 4104 blocked by firewall
2019-07-17 02:54:01
49.83.170.210 attackspambots
abuse-sasl
2019-07-17 02:33:37
94.41.196.254 attackspambots
Jul 16 20:00:59 legacy sshd[28557]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.41.196.254
Jul 16 20:01:01 legacy sshd[28557]: Failed password for invalid user luc from 94.41.196.254 port 58279 ssh2
Jul 16 20:07:53 legacy sshd[28767]: Failed password for root from 94.41.196.254 port 58566 ssh2
...
2019-07-17 02:26:50
118.194.132.112 attack
$f2bV_matches
2019-07-17 02:41:38

Recently Reported IPs

217.122.234.41 157.95.27.155 197.46.170.85 69.168.55.193
180.35.169.30 5.116.156.241 231.172.96.209 234.52.183.66
39.88.132.104 115.9.30.17 43.170.160.47 124.169.166.216
168.92.27.175 134.243.71.250 250.181.20.150 124.172.70.13
119.198.39.16 77.116.143.193 81.91.99.69 80.118.171.177