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

Region: Jilin

Country: China

Internet Service Provider: China Unicom Jilin Province Network

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

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

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 17 03:39:07 CST 2019
;; MSG SIZE  rcvd: 119
Host info
111.144.214.139.in-addr.arpa domain name pointer 111.144.214.139.adsl-pool.jlccptt.net.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
111.144.214.139.in-addr.arpa	name = 111.144.214.139.adsl-pool.jlccptt.net.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
27.155.87.43 attackspam
5964/tcp 5960/tcp 5928/tcp...
[2019-06-13/08-14]10pkt,4pt.(tcp)
2019-08-14 17:46:19
58.227.2.130 attackbots
Aug 14 07:54:38 XXX sshd[48174]: Invalid user client from 58.227.2.130 port 19188
2019-08-14 17:51:13
191.53.59.175 attackspambots
Aug 13 22:55:57 web1 postfix/smtpd[2090]: warning: unknown[191.53.59.175]: SASL PLAIN authentication failed: authentication failure
...
2019-08-14 17:20:21
62.43.51.144 attack
Automatic report - Port Scan Attack
2019-08-14 17:16:24
104.238.103.72 attack
xmlrpc attack
2019-08-14 17:25:36
142.93.15.179 attack
Automatic report - Banned IP Access
2019-08-14 17:28:40
167.114.3.44 attack
[portscan] Port scan
2019-08-14 18:00:59
185.200.117.18 attack
" "
2019-08-14 17:29:19
104.248.56.37 attackbotsspam
Aug 14 06:54:09 SilenceServices sshd[31013]: Failed password for root from 104.248.56.37 port 48378 ssh2
Aug 14 06:59:02 SilenceServices sshd[1966]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.56.37
Aug 14 06:59:04 SilenceServices sshd[1966]: Failed password for invalid user testftp from 104.248.56.37 port 41204 ssh2
2019-08-14 17:07:32
46.148.199.34 attackspambots
Aug 14 09:08:47 XXX sshd[55325]: Invalid user nagios1 from 46.148.199.34 port 34059
2019-08-14 17:49:26
111.230.249.77 attack
Aug 14 11:35:17 webhost01 sshd[31107]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.230.249.77
Aug 14 11:35:19 webhost01 sshd[31107]: Failed password for invalid user servercsgo from 111.230.249.77 port 55698 ssh2
...
2019-08-14 18:05:37
181.215.159.207 attackspam
(From eric@talkwithcustomer.com) Hello infinitehealth.biz,

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 infinitehealth.biz.
- 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 infinitehealth.biz, 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
2019-08-14 17:17:46
1.119.7.142 attackbotsspam
Aug 13 02:48:10 estefan sshd[18363]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.7.142  user=r.r
Aug 13 02:48:12 estefan sshd[18363]: Failed password for r.r from 1.119.7.142 port 12368 ssh2
Aug 13 02:48:12 estefan sshd[18364]: Received disconnect from 1.119.7.142: 11: Bye Bye
Aug 13 03:12:26 estefan sshd[19093]: Invalid user cactiuser from 1.119.7.142
Aug 13 03:12:26 estefan sshd[19093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.7.142 
Aug 13 03:12:28 estefan sshd[19093]: Failed password for invalid user cactiuser from 1.119.7.142 port 13657 ssh2
Aug 13 03:12:28 estefan sshd[19094]: Received disconnect from 1.119.7.142: 11: Bye Bye
Aug 13 03:17:19 estefan sshd[19158]: Invalid user knox from 1.119.7.142
Aug 13 03:17:19 estefan sshd[19158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.119.7.142 


........
-----------------------------------------------
https://www.
2019-08-14 17:44:28
112.53.194.155 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-08-14 17:46:03
189.68.223.202 attack
Aug 14 08:57:09 ncomp sshd[2342]: Invalid user helpdesk from 189.68.223.202
Aug 14 08:57:09 ncomp sshd[2342]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.68.223.202
Aug 14 08:57:09 ncomp sshd[2342]: Invalid user helpdesk from 189.68.223.202
Aug 14 08:57:11 ncomp sshd[2342]: Failed password for invalid user helpdesk from 189.68.223.202 port 33664 ssh2
2019-08-14 17:57:49

Recently Reported IPs

180.76.102.226 74.167.0.139 182.146.89.142 215.184.81.245
157.242.196.155 87.244.231.187 111.33.160.56 61.140.124.113
255.236.67.99 132.245.14.158 191.178.173.79 32.238.241.23
118.103.109.1 38.188.166.15 112.163.245.213 125.182.13.148
192.111.19.70 50.30.33.95 113.147.190.89 209.149.230.55