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

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.5.31.240 attack
[15/Dec/2019:07:29:20 +0100] Web-Request: "GET /wp-login.php", User-Agent: "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.1"
2019-12-15 16:02:38
139.5.31.27 attackbotsspam
Automatic report - Banned IP Access
2019-12-08 18:39:52
139.5.31.27 attackbotsspam
Port Scan
2019-10-30 01:36:59
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.5.31.194
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49877
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.5.31.194.			IN	A

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

;; Query time: 75 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:33:00 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 194.31.5.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 194.31.5.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.114.191.82 attack
Unauthorized connection attempt detected from IP address 92.114.191.82 to port 8080 [J]
2020-02-04 06:12:14
75.183.108.202 attackbots
Unauthorized connection attempt detected from IP address 75.183.108.202 to port 23 [J]
2020-02-04 06:15:01
176.212.114.122 attackspambots
Unauthorized connection attempt detected from IP address 176.212.114.122 to port 23 [J]
2020-02-04 06:26:28
118.239.9.173 attack
Unauthorized connection attempt detected from IP address 118.239.9.173 to port 80 [J]
2020-02-04 06:31:34
105.98.173.165 attackspambots
Unauthorized connection attempt detected from IP address 105.98.173.165 to port 80 [J]
2020-02-04 06:36:13
49.51.161.114 attackspam
Unauthorized connection attempt detected from IP address 49.51.161.114 to port 8182 [J]
2020-02-04 06:17:25
67.71.158.60 attack
Unauthorized connection attempt detected from IP address 67.71.158.60 to port 9000 [J]
2020-02-04 06:15:33
103.233.122.246 attackbots
Unauthorized connection attempt detected from IP address 103.233.122.246 to port 80 [J]
2020-02-04 06:36:39
91.235.75.129 attack
Unauthorized connection attempt detected from IP address 91.235.75.129 to port 1433 [J]
2020-02-04 06:12:36
176.114.46.39 attackspambots
Unauthorized connection attempt detected from IP address 176.114.46.39 to port 80 [J]
2020-02-04 06:26:58
123.20.163.73 attackspambots
Unauthorized connection attempt detected from IP address 123.20.163.73 to port 22 [J]
2020-02-04 06:29:49
197.45.181.18 attackbots
Unauthorized connection attempt detected from IP address 197.45.181.18 to port 23 [J]
2020-02-04 06:48:42
111.47.16.208 attack
Unauthorized connection attempt detected from IP address 111.47.16.208 to port 23 [J]
2020-02-04 06:35:38
113.161.222.82 attackbotsspam
Unauthorized connection attempt detected from IP address 113.161.222.82 to port 88 [J]
2020-02-04 06:34:21
177.89.199.53 attackbotsspam
Unauthorized connection attempt detected from IP address 177.89.199.53 to port 1433 [J]
2020-02-04 06:26:07

Recently Reported IPs

139.5.31.192 139.5.31.199 139.5.31.208 139.5.31.210
139.5.31.206 139.5.31.196 118.254.141.169 139.5.31.213
139.5.31.214 139.5.36.136 139.5.36.117 139.5.36.239
139.5.31.222 139.5.31.219 139.5.36.228 139.5.31.218
139.5.36.15 139.5.31.216 139.5.31.220 118.254.141.17