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: Viet Nam

Internet Service Provider: Vietnam Posts and Telecommunications Group

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
Type Details Datetime
attackspambots
Unauthorized connection attempt from IP address 14.160.29.66 on Port 445(SMB)
2020-04-28 18:49:03
attack
20/2/2@23:46:03: FAIL: Alarm-Network address from=14.160.29.66
...
2020-02-03 20:25:25
Comments on same subnet:
IP Type Details Datetime
14.160.29.42 attackbots
failed_logins
2020-08-02 18:01:41
14.160.29.42 attackbots
Dovecot Invalid User Login Attempt.
2020-07-07 16:18:07
14.160.29.42 attackspam
Dovecot Invalid User Login Attempt.
2020-06-27 20:21:43
14.160.29.42 attack
2020-05-0205:52:171jUjCK-0000M7-Fy\<=info@whatsup2013.chH=\(localhost\)[113.172.100.201]:34802P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:info@whatsup2013.chS=3059id=0e744e494269bc4f6c9264373ce8d1fdde343886ab@whatsup2013.chT="You'veeverbeenintruelove\?"forbglisson@rrisd.netquee1022@gmail.com2020-05-0205:52:361jUjCd-0000PA-5K\<=info@whatsup2013.chH=\(localhost\)[14.226.241.13]:51318P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:info@whatsup2013.chS=3126id=a5de31626942979bbcf94f1ce82f25291a466e29@whatsup2013.chT="Iamjustinlovewithyou"forusuiautumn@gmail.comahmed359901@gmail.com2020-05-0205:53:041jUjD5-0000RE-CP\<=info@whatsup2013.chH=\(localhost\)[14.187.121.142]:44772P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:info@whatsup2013.chS=3163id=888c3a696249636bf7f244e80ffbd1cd5f01fe@whatsup2013.chT="Youarefrommyfantasy"forrcolonna.mafp@gmail.combelcourt87@hotmail.com2020-05-0205:52:541jUjCv-0000Qh-0A\<=info@whatsup2013.chH=\(localhost\)
2020-05-02 16:07:11
14.160.29.22 attack
445/tcp
[2020-03-18]1pkt
2020-03-18 20:59:36
14.160.29.58 attackbots
Unauthorized connection attempt from IP address 14.160.29.58 on Port 445(SMB)
2020-03-11 03:38:42
14.160.29.246 attackbots
$f2bV_matches
2020-03-01 17:50:27
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.160.29.66
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35699
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;14.160.29.66.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 03 20:25:21 CST 2020
;; MSG SIZE  rcvd: 116
Host info
66.29.160.14.in-addr.arpa domain name pointer static.vnpt.vn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
66.29.160.14.in-addr.arpa	name = static.vnpt.vn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
147.139.132.146 attack
Dec 29 13:52:50 server sshd\[9298\]: Invalid user menashi from 147.139.132.146
Dec 29 13:52:50 server sshd\[9298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.139.132.146 
Dec 29 13:52:53 server sshd\[9298\]: Failed password for invalid user menashi from 147.139.132.146 port 33044 ssh2
Dec 29 14:05:18 server sshd\[12226\]: Invalid user ach from 147.139.132.146
Dec 29 14:05:18 server sshd\[12226\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.139.132.146 
...
2019-12-29 22:41:10
175.5.22.189 attack
Scanning
2019-12-29 22:49:11
172.81.248.249 attack
Dec 29 15:38:12 [host] sshd[27202]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.248.249  user=root
Dec 29 15:38:14 [host] sshd[27202]: Failed password for root from 172.81.248.249 port 56232 ssh2
Dec 29 15:39:42 [host] sshd[27456]: Invalid user webmaster from 172.81.248.249
2019-12-29 22:40:12
185.131.12.170 attack
Attempts against SMTP/SSMTP
2019-12-29 22:27:37
79.3.6.207 attack
Automatic report - SSH Brute-Force Attack
2019-12-29 22:10:22
78.188.21.128 attack
Unauthorized connection attempt detected from IP address 78.188.21.128 to port 23
2019-12-29 22:41:33
5.122.4.96 attack
[portscan] Port scan
2019-12-29 22:11:24
103.254.120.222 attackbots
Dec 29 09:30:55 mail sshd\[37497\]: Invalid user wwwrun from 103.254.120.222
Dec 29 09:30:55 mail sshd\[37497\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.120.222
...
2019-12-29 22:36:49
101.69.107.11 attackspam
Scanning
2019-12-29 22:13:36
103.118.49.11 attackbots
port scan and connect, tcp 1433 (ms-sql-s)
2019-12-29 22:47:20
144.217.243.216 attack
Dec 29 09:19:28 Invalid user mysql from 144.217.243.216 port 43492
2019-12-29 22:18:09
201.161.58.107 attackspam
5x Failed Password
2019-12-29 22:50:53
147.135.168.173 attackbotsspam
$f2bV_matches
2019-12-29 22:30:20
61.19.27.253 attack
Dec 29 13:47:51 sxvn sshd[1981902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.19.27.253
2019-12-29 22:35:59
107.173.209.21 attackbotsspam
(From eric@talkwithcustomer.com)  
Hey,

You have a website livewithvitality.com, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a
2019-12-29 22:44:33

Recently Reported IPs

204.190.128.240 104.158.58.91 146.128.241.91 14.27.103.46
176.231.6.152 80.14.234.172 214.168.245.70 123.22.140.22
124.157.40.245 145.46.51.129 93.161.153.169 119.34.28.142
170.210.203.201 60.96.23.187 135.157.210.99 136.97.182.73
101.86.144.206 80.183.83.123 210.203.8.46 38.82.26.10