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

;; QUESTION SECTION:
;104.16.0.18.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 06 23:32:57 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 18.0.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 18.0.16.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.52.68.79 attackbots
Feb 14 05:54:20 h2177944 kernel: \[4854021.137261\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=182.52.68.79 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=17326 DF PROTO=TCP SPT=57774 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 14 05:54:20 h2177944 kernel: \[4854021.137276\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=182.52.68.79 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=17326 DF PROTO=TCP SPT=57774 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 14 05:54:33 h2177944 kernel: \[4854034.210204\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=182.52.68.79 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=116 ID=16333 DF PROTO=TCP SPT=54206 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 14 05:54:33 h2177944 kernel: \[4854034.210221\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=182.52.68.79 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=116 ID=16333 DF PROTO=TCP SPT=54206 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 14 05:54:42 h2177944 kernel: \[4854042.737719\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=182.52.68.79 DST=85.21
2020-02-14 16:25:28
142.93.212.131 attackspambots
Feb 14 07:47:51 server sshd\[18559\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.212.131  user=root
Feb 14 07:47:53 server sshd\[18559\]: Failed password for root from 142.93.212.131 port 43070 ssh2
Feb 14 07:54:38 server sshd\[19426\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.212.131  user=root
Feb 14 07:54:40 server sshd\[19426\]: Failed password for root from 142.93.212.131 port 39034 ssh2
Feb 14 07:55:37 server sshd\[19916\]: Invalid user cstrike from 142.93.212.131
...
2020-02-14 16:09:26
66.96.239.167 attackbotsspam
Honeypot attack, port: 445, PTR: host-66-96-239-167.myrepublic.co.id.
2020-02-14 16:44:37
117.5.227.171 attackbots
1581656106 - 02/14/2020 05:55:06 Host: 117.5.227.171/117.5.227.171 Port: 445 TCP Blocked
2020-02-14 16:44:11
200.86.33.140 attackbotsspam
Invalid user sih from 200.86.33.140 port 57842
2020-02-14 16:24:42
177.37.81.138 attack
DATE:2020-02-14 05:55:10, IP:177.37.81.138, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2020-02-14 16:37:30
172.245.103.137 attack
(From eric@talkwithcustomer.com) Hello bowerschiro.net,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website bowerschiro.net.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website bowerschiro.net, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famous marketer
2020-02-14 16:15:23
201.190.176.19 attack
Feb 14 06:03:24 thevastnessof sshd[20833]: Failed password for root from 201.190.176.19 port 56830 ssh2
...
2020-02-14 16:31:29
104.244.79.250 attackbotsspam
Invalid user fake from 104.244.79.250 port 34306
2020-02-14 16:29:28
119.42.99.35 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-14 16:19:51
14.186.214.22 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 14-02-2020 04:55:09.
2020-02-14 16:39:14
189.5.161.144 attackspambots
Invalid user Gingers from 189.5.161.144 port 49830
2020-02-14 16:34:03
117.95.191.144 attack
Automatic report - Port Scan Attack
2020-02-14 16:38:32
185.217.170.25 attackbotsspam
(From eric@talkwithcustomer.com) Hello bowerschiro.net,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website bowerschiro.net.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website bowerschiro.net, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famous marketer
2020-02-14 16:16:07
106.12.48.44 attack
Feb 13 19:30:06 php1 sshd\[11379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.48.44  user=root
Feb 13 19:30:08 php1 sshd\[11379\]: Failed password for root from 106.12.48.44 port 37217 ssh2
Feb 13 19:33:30 php1 sshd\[11646\]: Invalid user verity from 106.12.48.44
Feb 13 19:33:30 php1 sshd\[11646\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.48.44
Feb 13 19:33:32 php1 sshd\[11646\]: Failed password for invalid user verity from 106.12.48.44 port 44728 ssh2
2020-02-14 16:08:33

Recently Reported IPs

104.16.0.16 104.16.0.2 104.16.0.20 104.16.0.22
104.16.0.24 104.16.0.26 104.16.0.27 104.16.0.28
104.16.0.29 104.16.0.3 104.16.0.31 104.16.0.32
104.16.0.33 104.16.0.34 104.16.0.35 104.16.0.36
104.16.0.37 173.192.21.89 104.16.0.39 104.16.0.4