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:
IP Type Details Datetime
139.219.11.254 attackspambots
2020-10-07T04:24:28.732143billing sshd[11343]: Failed password for root from 139.219.11.254 port 58792 ssh2
2020-10-07T04:29:16.495199billing sshd[22178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.11.254  user=root
2020-10-07T04:29:18.811131billing sshd[22178]: Failed password for root from 139.219.11.254 port 60970 ssh2
...
2020-10-07 07:24:26
139.219.11.254 attack
Oct  6 10:40:55 mail sshd[6207]: Failed password for root from 139.219.11.254 port 56568 ssh2
...
2020-10-06 23:48:20
139.219.11.254 attack
SSH Brute-Force Attack
2020-10-06 15:36:41
139.219.11.254 attackbots
Oct  1 15:13:08 mellenthin sshd[25510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.11.254  user=root
Oct  1 15:13:10 mellenthin sshd[25510]: Failed password for invalid user root from 139.219.11.254 port 45166 ssh2
2020-10-02 02:53:29
139.219.11.254 attackspam
$f2bV_matches
2020-10-01 19:04:50
139.219.11.254 attack
Sep 19 22:42:08 NG-HHDC-SVS-001 sshd[23649]: Invalid user test from 139.219.11.254
...
2020-09-19 23:17:45
139.219.11.254 attackbots
SSH brutforce
2020-09-19 06:43:21
139.219.11.254 attackbots
Aug  2 05:22:11 firewall sshd[10420]: Failed password for root from 139.219.11.254 port 57802 ssh2
Aug  2 05:26:39 firewall sshd[10528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.11.254  user=root
Aug  2 05:26:41 firewall sshd[10528]: Failed password for root from 139.219.11.254 port 58026 ssh2
...
2020-08-02 16:36:19
139.219.11.254 attackspambots
2020-07-25T11:06:35.235992mail.broermann.family sshd[10873]: Invalid user xin from 139.219.11.254 port 38752
2020-07-25T11:06:35.241278mail.broermann.family sshd[10873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.11.254
2020-07-25T11:06:35.235992mail.broermann.family sshd[10873]: Invalid user xin from 139.219.11.254 port 38752
2020-07-25T11:06:36.729357mail.broermann.family sshd[10873]: Failed password for invalid user xin from 139.219.11.254 port 38752 ssh2
2020-07-25T11:12:18.211298mail.broermann.family sshd[11119]: Invalid user zipcode from 139.219.11.254 port 49024
...
2020-07-25 19:11:00
139.219.11.254 attackbotsspam
$f2bV_matches
2020-07-04 05:23:00
139.219.11.254 attackbotsspam
$f2bV_matches
2020-05-26 22:42:09
139.219.11.254 attackspam
May 15 06:20:39 : SSH login attempts with invalid user
2020-05-16 06:29:03
139.219.11.254 attack
May 12 11:40:25 xeon sshd[17353]: Failed password for invalid user mu from 139.219.11.254 port 46750 ssh2
2020-05-12 19:06:39
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.219.11.213
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58066
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.219.11.213.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:38:53 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 213.11.219.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 213.11.219.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
123.130.109.186 attack
Unauthorized connection attempt detected from IP address 123.130.109.186 to port 81 [T]
2020-01-17 07:01:18
90.15.133.8 attackbotsspam
Unauthorized connection attempt detected from IP address 90.15.133.8 to port 81 [T]
2020-01-17 07:10:07
27.2.100.201 attackspam
Unauthorized connection attempt detected from IP address 27.2.100.201 to port 5555 [J]
2020-01-17 07:18:16
49.235.5.243 attackspam
Unauthorized connection attempt detected from IP address 49.235.5.243 to port 22 [T]
2020-01-17 07:12:59
111.42.103.37 attackspam
Unauthorized connection attempt detected from IP address 111.42.103.37 to port 23 [T]
2020-01-17 07:08:55
1.1.134.79 attack
Unauthorized connection attempt detected from IP address 1.1.134.79 to port 4567 [T]
2020-01-17 06:50:34
120.77.244.21 attackspam
Unauthorized connection attempt detected from IP address 120.77.244.21 to port 7001 [T]
2020-01-17 07:02:33
180.218.242.170 attackspambots
Unauthorized connection attempt detected from IP address 180.218.242.170 to port 23 [J]
2020-01-17 06:55:40
164.52.24.174 attack
Unauthorized connection attempt detected from IP address 164.52.24.174 to port 789 [J]
2020-01-17 06:58:28
223.15.212.140 attackbots
Unauthorized connection attempt detected from IP address 223.15.212.140 to port 23 [J]
2020-01-17 06:50:53
42.117.25.97 attack
Unauthorized connection attempt detected from IP address 42.117.25.97 to port 23 [J]
2020-01-17 06:47:29
206.189.35.254 attackbotsspam
Invalid user nadmin from 206.189.35.254 port 60094
2020-01-17 06:53:30
106.75.84.197 attackbotsspam
Unauthorized connection attempt detected from IP address 106.75.84.197 to port 1521 [J]
2020-01-17 07:09:21
47.103.37.133 attackspam
Unauthorized connection attempt detected from IP address 47.103.37.133 to port 22 [T]
2020-01-17 06:45:32
47.108.68.163 attackbots
Unauthorized connection attempt detected from IP address 47.108.68.163 to port 22 [T]
2020-01-17 07:13:39

Recently Reported IPs

139.219.13.226 139.219.17.209 139.219.146.219 139.219.60.185
139.220.193.166 139.219.17.229 139.219.189.163 139.223.22.2
139.224.116.9 139.224.111.89 139.224.105.228 139.224.10.206
139.224.129.20 139.224.186.122 139.224.172.148 139.224.134.65
139.224.194.56 139.224.186.226 139.224.189.44 139.224.191.195