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

;; QUESTION SECTION:
;104.18.16.101.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 08 02:26:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 101.16.18.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 101.16.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
85.243.128.8 attackbots
Mar 19 00:14:58 silence02 sshd[23274]: Failed password for root from 85.243.128.8 port 50894 ssh2
Mar 19 00:17:47 silence02 sshd[23488]: Failed password for root from 85.243.128.8 port 51220 ssh2
2020-03-19 09:32:49
180.76.102.136 attackbots
Mar 18 20:13:41 firewall sshd[24111]: Failed password for invalid user kafka from 180.76.102.136 port 50578 ssh2
Mar 18 20:16:09 firewall sshd[24267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.102.136  user=root
Mar 18 20:16:12 firewall sshd[24267]: Failed password for root from 180.76.102.136 port 37954 ssh2
...
2020-03-19 09:09:11
49.232.51.237 attackspam
SSH brute force
2020-03-19 09:05:49
222.186.42.75 attackbots
Mar 18 22:10:46 firewall sshd[9890]: Failed password for root from 222.186.42.75 port 22040 ssh2
Mar 18 22:10:49 firewall sshd[9890]: Failed password for root from 222.186.42.75 port 22040 ssh2
Mar 18 22:10:51 firewall sshd[9890]: Failed password for root from 222.186.42.75 port 22040 ssh2
...
2020-03-19 09:18:06
190.24.6.162 attack
SSH Bruteforce attack
2020-03-19 09:23:08
121.204.145.50 attackbotsspam
" "
2020-03-19 08:54:40
14.18.107.61 attack
Mar 19 00:06:18 sd-53420 sshd\[30960\]: Invalid user re from 14.18.107.61
Mar 19 00:06:18 sd-53420 sshd\[30960\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.18.107.61
Mar 19 00:06:20 sd-53420 sshd\[30960\]: Failed password for invalid user re from 14.18.107.61 port 43656 ssh2
Mar 19 00:09:52 sd-53420 sshd\[32173\]: User root from 14.18.107.61 not allowed because none of user's groups are listed in AllowGroups
Mar 19 00:09:52 sd-53420 sshd\[32173\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.18.107.61  user=root
...
2020-03-19 09:26:08
137.118.22.77 attackbotsspam
Received: from mailproxy12.neonova.net ([137.118.22.77])
          by smtp.email-protect.gosecure.net ({b5689ac8-335f-11ea-a228-691fa47b4314})
          via TCP (outbound) with ESMTP id 20200318195910888_00000620;
          Wed, 18 Mar 2020 12:59:10 -0700
X-RC-FROM: 
Received: from nvl-mbs60.neonova.net (nvl-mbs60.neonova.net [137.118.23.60])
	by mailproxy12.neonova.net (Postfix) with ESMTP id 2F51A365917;
	Wed, 18 Mar 2020 15:58:15 -0400 (EDT)
Date: Wed, 18 Mar 2020 15:58:15 -0400 (EDT)
From: "ibank.nbg.gr" 
Reply-To: "ibank.nbg.gr" 
To: Upstart Team 
Message-ID: <154744878.289354838.1584561495076.JavaMail.zimbra@hancock.net>

Pretending n.b.g bank to hack login passwords - account
2020-03-19 08:58:30
24.20.244.45 attackspambots
Mar 18 22:13:05 *** sshd[15559]: Invalid user sinusbot from 24.20.244.45
2020-03-19 09:07:20
134.209.16.36 attackspambots
Mar 19 01:05:56 serwer sshd\[20049\]: Invalid user user from 134.209.16.36 port 35880
Mar 19 01:05:56 serwer sshd\[20049\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.16.36
Mar 19 01:05:58 serwer sshd\[20049\]: Failed password for invalid user user from 134.209.16.36 port 35880 ssh2
...
2020-03-19 08:52:30
178.128.255.8 attackspam
Mar 19 01:18:51 serwer sshd\[21300\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.255.8  user=root
Mar 19 01:18:52 serwer sshd\[21300\]: Failed password for root from 178.128.255.8 port 42588 ssh2
Mar 19 01:24:15 serwer sshd\[21851\]: User nobody from 178.128.255.8 not allowed because not listed in AllowUsers
Mar 19 01:24:15 serwer sshd\[21851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.255.8  user=nobody
...
2020-03-19 09:02:59
159.203.107.212 attack
159.203.107.212 - - [18/Mar/2020:22:00:06 +0100] "POST /wp-login.php HTTP/1.1" 200 7362 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
159.203.107.212 - - [18/Mar/2020:22:00:08 +0100] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
159.203.107.212 - - [19/Mar/2020:01:34:34 +0100] "GET /wp-login.php HTTP/1.1" 200 5806 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-03-19 09:06:49
128.199.155.218 attackbots
invalid login attempt (louis)
2020-03-19 09:28:13
183.178.39.73 attackbotsspam
port scan and connect, tcp 1433 (ms-sql-s)
2020-03-19 09:27:18
194.186.180.118 attackspambots
Microsoft-Windows-Security-Auditing
2020-03-19 09:13:23

Recently Reported IPs

104.18.159.253 104.18.16.77 104.18.17.77 104.18.171.237
104.18.172.237 104.18.174.100 104.18.182.4 104.18.197.63
104.18.198.63 104.18.217.85 104.18.218.85 104.18.22.228
104.18.23.228 104.18.235.62 104.18.236.236 104.18.236.62
104.18.237.236 104.18.36.80 104.18.37.183 104.18.37.197