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

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

;; QUESTION SECTION:
;104.16.9.142.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 01:10:29 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 142.9.16.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 142.9.16.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
118.163.245.230 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-08-29 20:49:29
104.236.112.52 attackspambots
Automatic report - Banned IP Access
2019-08-29 21:01:47
209.97.161.124 attack
Aug 29 13:09:44 XXX sshd[62814]: Invalid user ys from 209.97.161.124 port 59306
2019-08-29 21:17:29
118.24.210.254 attackbots
Aug 29 15:30:13 yabzik sshd[21959]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.210.254
Aug 29 15:30:14 yabzik sshd[21959]: Failed password for invalid user wave from 118.24.210.254 port 35640 ssh2
Aug 29 15:33:10 yabzik sshd[22885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.210.254
2019-08-29 20:39:18
178.128.194.116 attackbots
Aug 29 00:47:29 sachi sshd\[9480\]: Invalid user Administrator123 from 178.128.194.116
Aug 29 00:47:29 sachi sshd\[9480\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.194.116
Aug 29 00:47:31 sachi sshd\[9480\]: Failed password for invalid user Administrator123 from 178.128.194.116 port 53374 ssh2
Aug 29 00:54:12 sachi sshd\[10072\]: Invalid user 12345 from 178.128.194.116
Aug 29 00:54:12 sachi sshd\[10072\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.194.116
2019-08-29 20:53:11
129.121.176.210 attack
WordPress login Brute force / Web App Attack on client site.
2019-08-29 20:50:15
115.236.100.114 attackbotsspam
$f2bV_matches
2019-08-29 20:44:47
178.62.79.227 attack
$f2bV_matches
2019-08-29 20:53:53
211.22.154.223 attackbots
Aug 29 08:49:12 debian sshd\[695\]: Invalid user cape from 211.22.154.223 port 60110
Aug 29 08:49:12 debian sshd\[695\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.22.154.223
Aug 29 08:49:14 debian sshd\[695\]: Failed password for invalid user cape from 211.22.154.223 port 60110 ssh2
...
2019-08-29 20:52:13
93.29.187.145 attackbots
Aug 29 02:07:47 sachi sshd\[16656\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.187.29.93.rev.sfr.net  user=root
Aug 29 02:07:49 sachi sshd\[16656\]: Failed password for root from 93.29.187.145 port 51254 ssh2
Aug 29 02:11:51 sachi sshd\[17058\]: Invalid user panasonic from 93.29.187.145
Aug 29 02:11:51 sachi sshd\[17058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.187.29.93.rev.sfr.net
Aug 29 02:11:53 sachi sshd\[17058\]: Failed password for invalid user panasonic from 93.29.187.145 port 38274 ssh2
2019-08-29 20:21:54
212.227.200.232 attackspam
Aug 29 03:11:48 wbs sshd\[16778\]: Invalid user pentaho from 212.227.200.232
Aug 29 03:11:48 wbs sshd\[16778\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.227.200.232
Aug 29 03:11:51 wbs sshd\[16778\]: Failed password for invalid user pentaho from 212.227.200.232 port 38564 ssh2
Aug 29 03:15:47 wbs sshd\[17136\]: Invalid user guest from 212.227.200.232
Aug 29 03:15:47 wbs sshd\[17136\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.227.200.232
2019-08-29 21:23:33
176.119.141.251 attackbotsspam
NAME : GB-BLOCKCHAINNETWORKSOLUTIONS + e-mail abuse : abuse@blockchainnetworksolutions.co.uk CIDR : 176.119.141.0/24 | STATUS : 403 {Looking for resource vulnerabilities} DDoS Attack GB - block certain countries :) IP: 176.119.141.251  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-08-29 20:28:19
139.198.122.90 attack
2019-08-29T11:00:44.922321abusebot-2.cloudsearch.cf sshd\[32743\]: Invalid user marius from 139.198.122.90 port 48376
2019-08-29 20:37:55
106.52.235.249 attack
SSH Bruteforce attempt
2019-08-29 20:20:31
14.177.178.5 attack
Unauthorised access (Aug 29) SRC=14.177.178.5 LEN=52 TTL=116 ID=20706 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-29 20:43:13

Recently Reported IPs

104.16.9.141 104.16.9.143 104.16.9.144 104.16.9.145
104.16.9.146 104.16.9.72 104.16.9.97 104.16.9.98
104.16.9.99 104.16.90.125 104.16.90.38 104.16.90.58
104.16.91.125 104.16.94.17 104.16.95.17 104.16.99.36
104.160.14.127 104.160.171.87 104.160.180.111 104.160.180.118