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

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

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

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sun Jul 14 11:20:02 CST 2019
;; MSG SIZE  rcvd: 117
Host info
Host 139.55.44.113.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 139.55.44.113.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.176.27.246 attackbotsspam
10.07.2019 21:50:53 Connection to port 9989 blocked by firewall
2019-07-11 06:40:04
125.90.52.63 attackbots
19/7/10@16:01:17: FAIL: Alarm-SSH address from=125.90.52.63
...
2019-07-11 06:03:02
177.184.75.130 attackbotsspam
Automatic report - SSH Brute-Force Attack
2019-07-11 06:37:10
103.219.61.3 attack
Jul 11 02:01:27 areeb-Workstation sshd\[31053\]: Invalid user media from 103.219.61.3
Jul 11 02:01:27 areeb-Workstation sshd\[31053\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.61.3
Jul 11 02:01:30 areeb-Workstation sshd\[31053\]: Failed password for invalid user media from 103.219.61.3 port 41760 ssh2
...
2019-07-11 06:05:48
113.17.111.19 attack
Jul 10 21:03:17 giegler sshd[27899]: Invalid user julian from 113.17.111.19 port 2395
Jul 10 21:03:17 giegler sshd[27899]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.17.111.19
Jul 10 21:03:17 giegler sshd[27899]: Invalid user julian from 113.17.111.19 port 2395
Jul 10 21:03:20 giegler sshd[27899]: Failed password for invalid user julian from 113.17.111.19 port 2395 ssh2
Jul 10 21:05:07 giegler sshd[28000]: Invalid user teamspeak from 113.17.111.19 port 2396
2019-07-11 06:26:15
218.92.0.157 attackbotsspam
Jul 10 15:05:42 debian sshd\[29802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.157  user=root
Jul 10 15:05:43 debian sshd\[29802\]: Failed password for root from 218.92.0.157 port 49280 ssh2
Jul 10 15:05:46 debian sshd\[29802\]: Failed password for root from 218.92.0.157 port 49280 ssh2
...
2019-07-11 05:57:59
18.222.253.127 attackbotsspam
Attempt to run wp-login.php
2019-07-11 06:27:19
88.26.236.2 attack
2019-07-10T22:08:48.532516abusebot-8.cloudsearch.cf sshd\[19933\]: Invalid user test from 88.26.236.2 port 47036
2019-07-11 06:15:02
190.223.26.38 attackspambots
Jul 10 19:02:07 ip-172-31-1-72 sshd\[1698\]: Invalid user sftp from 190.223.26.38
Jul 10 19:02:07 ip-172-31-1-72 sshd\[1698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.223.26.38
Jul 10 19:02:09 ip-172-31-1-72 sshd\[1698\]: Failed password for invalid user sftp from 190.223.26.38 port 12153 ssh2
Jul 10 19:04:43 ip-172-31-1-72 sshd\[1720\]: Invalid user john from 190.223.26.38
Jul 10 19:04:43 ip-172-31-1-72 sshd\[1720\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.223.26.38
2019-07-11 06:21:22
159.65.162.182 attackspambots
Jul 10 23:25:58 * sshd[5295]: Failed password for root from 159.65.162.182 port 35658 ssh2
2019-07-11 06:02:10
149.129.137.196 attack
ssh failed login
2019-07-11 06:39:12
119.146.223.134 attack
2019-07-10T05:31:46.320954stt-1.[munged] kernel: [6782727.803420] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:97:36:58:84:78:ac:57:a8:41:08:00 SRC=119.146.223.134 DST=[mungedIP1] LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=4223 PROTO=TCP SPT=50515 DPT=3306 WINDOW=1024 RES=0x00 SYN URGP=0 
2019-07-10T07:51:19.782949stt-1.[munged] kernel: [6791101.239817] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:97:36:58:84:78:ac:57:aa:c1:08:00 SRC=119.146.223.134 DST=[mungedIP1] LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=5675 PROTO=TCP SPT=59382 DPT=3389 WINDOW=1024 RES=0x00 SYN URGP=0 
2019-07-10T15:05:01.237707stt-1.[munged] kernel: [6817122.609922] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:97:36:58:84:78:ac:57:a8:41:08:00 SRC=119.146.223.134 DST=[mungedIP1] LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=15582 PROTO=TCP SPT=44581 DPT=3389 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-11 06:32:51
219.233.49.39 attackspambots
Automatic report - Web App Attack
2019-07-11 06:20:54
222.165.224.167 attackspam
19/7/10@15:05:40: FAIL: Alarm-Intrusion address from=222.165.224.167
...
2019-07-11 06:02:44
14.181.231.208 attackbotsspam
Unauthorized connection attempt from IP address 14.181.231.208 on Port 445(SMB)
2019-07-11 06:33:21

Recently Reported IPs

212.142.217.57 173.232.166.33 58.74.111.106 35.93.181.203
191.53.199.164 149.166.225.144 163.247.114.180 18.30.126.18
66.69.80.185 176.123.56.66 188.184.40.54 18.176.63.191
213.74.133.10 62.203.231.248 118.70.190.101 153.159.121.160
83.252.175.1 222.239.170.194 206.159.158.154 1.47.135.112