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

;; QUESTION SECTION:
;139.214.147.68.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 15:16:06 CST 2022
;; MSG SIZE  rcvd: 107
Host info
68.147.214.139.in-addr.arpa domain name pointer 68.147.214.139.adsl-pool.jlccptt.net.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
179.191.237.172 attackbots
SSH login attempts.
2020-04-17 20:31:16
49.234.147.154 attackbots
Apr 17 12:57:06 ncomp sshd[9010]: Invalid user tf from 49.234.147.154
Apr 17 12:57:06 ncomp sshd[9010]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.147.154
Apr 17 12:57:06 ncomp sshd[9010]: Invalid user tf from 49.234.147.154
Apr 17 12:57:08 ncomp sshd[9010]: Failed password for invalid user tf from 49.234.147.154 port 47394 ssh2
2020-04-17 20:11:22
51.83.42.66 attackbots
SSH Brute-Force reported by Fail2Ban
2020-04-17 19:49:29
45.40.201.5 attack
Apr 17 14:13:16 eventyay sshd[14234]: Failed password for root from 45.40.201.5 port 49020 ssh2
Apr 17 14:16:23 eventyay sshd[14328]: Failed password for root from 45.40.201.5 port 49960 ssh2
...
2020-04-17 20:24:26
95.216.139.24 attackbotsspam
Fail2Ban Ban Triggered (2)
2020-04-17 19:53:20
49.234.212.177 attackbots
Bruteforce detected by fail2ban
2020-04-17 20:24:09
134.209.185.131 attack
Apr 17 10:56:53 *** sshd[12763]: Invalid user postgres from 134.209.185.131
2020-04-17 20:27:36
167.71.7.119 attack
Apr 17 15:12:28 www5 sshd\[14645\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.7.119  user=root
Apr 17 15:12:30 www5 sshd\[14645\]: Failed password for root from 167.71.7.119 port 55006 ssh2
Apr 17 15:16:32 www5 sshd\[15455\]: Invalid user so from 167.71.7.119
...
2020-04-17 20:25:03
109.93.67.40 attack
Apr 17 12:54:24 v22018086721571380 sshd[30445]: Failed password for invalid user oo from 109.93.67.40 port 37326 ssh2
2020-04-17 19:52:48
182.61.52.46 attackbots
detected by Fail2Ban
2020-04-17 20:18:03
181.120.246.83 attackspambots
Invalid user ur from 181.120.246.83 port 49634
2020-04-17 20:14:19
51.89.235.112 attackspam
51.89.235.112 was recorded 12 times by 2 hosts attempting to connect to the following ports: 5064,5080,5078,5087,5061,5063,5066,5068,5077,5088,5060. Incident counter (4h, 24h, all-time): 12, 33, 209
2020-04-17 20:30:54
103.85.11.11 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-04-17 20:18:21
79.124.62.66 attack
Fail2Ban Ban Triggered
2020-04-17 20:00:35
1.234.53.32 attackspam
Automatic report - WordPress Brute Force
2020-04-17 20:06:18

Recently Reported IPs

129.195.141.122 218.197.250.11 58.82.233.101 116.205.59.165
170.95.16.157 183.48.244.47 147.227.46.96 175.239.163.74
217.16.2.146 131.44.195.52 122.206.178.146 108.234.225.255
44.199.172.22 53.176.203.117 19.167.29.79 202.155.244.118
112.224.211.149 156.181.104.184 3.38.216.232 52.195.180.173