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: China

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

;; QUESTION SECTION:
;14.204.169.105.			IN	A

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

;; Query time: 149 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 14:39:39 CST 2022
;; MSG SIZE  rcvd: 107
Host info
b'Host 105.169.204.14.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
server can't find 14.204.169.105.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
46.38.144.202 attackspam
2019-11-04T13:54:28.130933mail01 postfix/smtpd[6021]: warning: unknown[46.38.144.202]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-04T13:54:51.061582mail01 postfix/smtpd[6021]: warning: unknown[46.38.144.202]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-04T13:55:15.138037mail01 postfix/smtpd[6021]: warning: unknown[46.38.144.202]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-04 21:12:44
198.46.225.100 attackspambots
(From eric@talkwithcustomer.com) Hey,

You have a website naturalhealthdcs.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 st
2019-11-04 21:06:21
119.75.24.68 attackbots
Nov  4 10:22:53 lnxded63 sshd[10875]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.75.24.68
2019-11-04 21:23:58
142.93.214.130 attackbots
Nov  4 07:19:07 tux postfix/smtpd[16855]: connect from unknown[142.93.214.130]
Nov  4 07:19:08 tux postfix/smtpd[16855]: Anonymous TLS connection established from unknown[142.93.214.130]: TLSv1.2 whostnameh cipher AECDH-AES256-SHA (256/256 bhostnames)
Nov x@x
Nov x@x
Nov  4 07:19:11 tux postfix/smtpd[16855]: 5AF49B0001: client=unknown[142.93.214.130]
Nov  4 07:19:11 tux postfix/smtpd[16855]: disconnect from unknown[142.93.214.130]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=142.93.214.130
2019-11-04 21:36:47
67.55.25.57 attack
SSH/22 MH Probe, BF, Hack -
2019-11-04 21:28:02
123.30.249.104 attackspambots
2019-11-04T08:35:53.064796shield sshd\[5284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.30.249.104  user=root
2019-11-04T08:35:54.865667shield sshd\[5284\]: Failed password for root from 123.30.249.104 port 37200 ssh2
2019-11-04T08:40:28.799852shield sshd\[5939\]: Invalid user tester from 123.30.249.104 port 45942
2019-11-04T08:40:28.805358shield sshd\[5939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.30.249.104
2019-11-04T08:40:30.360034shield sshd\[5939\]: Failed password for invalid user tester from 123.30.249.104 port 45942 ssh2
2019-11-04 21:20:41
51.77.157.78 attackspambots
Nov  4 09:27:40 minden010 sshd[7166]: Failed password for root from 51.77.157.78 port 44974 ssh2
Nov  4 09:31:22 minden010 sshd[10934]: Failed password for root from 51.77.157.78 port 54108 ssh2
Nov  4 09:34:57 minden010 sshd[14548]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.157.78
...
2019-11-04 21:10:17
125.83.92.36 attackbotsspam
firewall-block, port(s): 1433/tcp
2019-11-04 21:41:21
54.67.50.2 attack
Connection by 54.67.50.2 on port: 6066 got caught by honeypot at 11/4/2019 5:21:21 AM
2019-11-04 21:22:23
106.12.189.235 attackspam
failed root login
2019-11-04 21:12:00
122.199.152.114 attackspambots
$f2bV_matches
2019-11-04 21:15:08
106.87.96.126 attackbots
FTP Brute Force
2019-11-04 21:19:28
190.215.112.122 attackbots
" "
2019-11-04 21:17:22
104.200.110.181 attack
$f2bV_matches
2019-11-04 21:30:43
180.251.115.44 attackspambots
2019-11-04T07:20:59.170448mail01 postfix/smtpd[16529]: warning: unknown[180.251.115.44]: SASL PLAIN authentication failed:
2019-11-04T07:21:05.352761mail01 postfix/smtpd[16529]: warning: unknown[180.251.115.44]: SASL PLAIN authentication failed:
2019-11-04T07:21:12.209946mail01 postfix/smtpd[16529]: warning: unknown[180.251.115.44]: SASL PLAIN authentication failed:
2019-11-04 21:25:33

Recently Reported IPs

14.207.176.211 14.207.176.180 14.207.163.114 14.205.71.118
14.207.203.244 14.207.181.194 14.207.206.151 14.207.205.238
14.207.23.150 14.207.176.3 14.207.23.198 14.207.181.241
14.207.51.157 14.207.42.251 153.184.178.209 14.207.60.231
14.207.18.68 14.207.7.36 14.207.70.41 14.207.41.173