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

;; QUESTION SECTION:
;104.94.182.142.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:36:34 CST 2023
;; MSG SIZE  rcvd: 107
Host info
142.182.94.104.in-addr.arpa domain name pointer a104-94-182-142.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
142.182.94.104.in-addr.arpa	name = a104-94-182-142.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.211.107.82 attackspambots
20 attempts against mh-ssh on storm
2020-06-28 14:06:48
160.153.153.29 attack
C2,WP GET /staging/wp-includes/wlwmanifest.xml
2020-06-28 13:54:25
92.53.65.188 attack
Jun 28 07:50:05 debian-2gb-nbg1-2 kernel: \[15582054.594387\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.53.65.188 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=39812 PROTO=TCP SPT=53067 DPT=33305 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-28 13:59:23
51.38.130.242 attackspambots
2020-06-28T05:16:33.138419shield sshd\[16753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=242.ip-51-38-130.eu  user=root
2020-06-28T05:16:34.716564shield sshd\[16753\]: Failed password for root from 51.38.130.242 port 52486 ssh2
2020-06-28T05:19:56.021080shield sshd\[18050\]: Invalid user oracle from 51.38.130.242 port 51724
2020-06-28T05:19:56.024764shield sshd\[18050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=242.ip-51-38-130.eu
2020-06-28T05:19:57.476908shield sshd\[18050\]: Failed password for invalid user oracle from 51.38.130.242 port 51724 ssh2
2020-06-28 13:32:07
62.234.164.238 attackspam
Invalid user cjd from 62.234.164.238 port 39720
2020-06-28 13:37:51
116.196.73.159 attackspambots
" "
2020-06-28 13:55:21
94.23.33.22 attackbotsspam
Jun 28 05:28:59 onepixel sshd[783195]: Invalid user ha from 94.23.33.22 port 50220
Jun 28 05:28:59 onepixel sshd[783195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.33.22 
Jun 28 05:28:59 onepixel sshd[783195]: Invalid user ha from 94.23.33.22 port 50220
Jun 28 05:29:01 onepixel sshd[783195]: Failed password for invalid user ha from 94.23.33.22 port 50220 ssh2
Jun 28 05:31:00 onepixel sshd[784390]: Invalid user user from 94.23.33.22 port 56310
2020-06-28 13:40:36
209.141.59.184 attackbots
(sshd) Failed SSH login from 209.141.59.184 (US/United States/LIFESHELELE.XYZ): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 28 07:10:45 amsweb01 sshd[28051]: Did not receive identification string from 209.141.59.184 port 60550
Jun 28 07:12:46 amsweb01 sshd[28441]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.59.184  user=admin
Jun 28 07:12:49 amsweb01 sshd[28441]: Failed password for admin from 209.141.59.184 port 57490 ssh2
Jun 28 07:14:45 amsweb01 sshd[28801]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.59.184  user=admin
Jun 28 07:14:47 amsweb01 sshd[28801]: Failed password for admin from 209.141.59.184 port 39456 ssh2
2020-06-28 13:49:27
222.239.124.19 attackbotsspam
SSH Brute-Forcing (server2)
2020-06-28 13:38:35
185.100.87.41 attack
Automatic report - Banned IP Access
2020-06-28 14:03:26
79.137.163.43 attackspambots
(sshd) Failed SSH login from 79.137.163.43 (RU/Russia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 28 05:44:29 grace sshd[3147]: Invalid user ckc from 79.137.163.43 port 52916
Jun 28 05:44:31 grace sshd[3147]: Failed password for invalid user ckc from 79.137.163.43 port 52916 ssh2
Jun 28 05:50:41 grace sshd[4167]: Invalid user nr from 79.137.163.43 port 38102
Jun 28 05:50:43 grace sshd[4167]: Failed password for invalid user nr from 79.137.163.43 port 38102 ssh2
Jun 28 05:55:21 grace sshd[4720]: Invalid user grafana from 79.137.163.43 port 37038
2020-06-28 13:42:48
51.77.144.50 attackspam
Jun 28 05:52:14 buvik sshd[13903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.144.50
Jun 28 05:52:16 buvik sshd[13903]: Failed password for invalid user ftpuser from 51.77.144.50 port 51458 ssh2
Jun 28 05:55:19 buvik sshd[14373]: Invalid user joanna from 51.77.144.50
...
2020-06-28 13:47:13
176.122.169.95 attackbots
Invalid user admin from 176.122.169.95 port 40638
2020-06-28 13:37:28
218.92.0.251 attackspambots
$f2bV_matches
2020-06-28 13:38:10
159.65.174.81 attack
" "
2020-06-28 13:26:04

Recently Reported IPs

104.94.237.6 104.94.231.190 104.94.208.39 104.94.150.167
104.94.181.129 104.94.52.148 104.94.172.255 104.94.57.57
104.94.245.84 104.94.24.48 104.94.71.108 104.94.78.11
104.94.53.73 104.94.34.12 104.94.45.29 104.94.72.168
104.94.50.5 104.94.196.234 104.94.8.81 104.94.61.204