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

;; QUESTION SECTION:
;139.5.31.210.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:33:01 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 210.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 210.31.5.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
110.93.247.108 attackbotsspam
Unauthorized connection attempt from IP address 110.93.247.108 on Port 445(SMB)
2020-02-13 02:42:15
77.247.108.14 attackbotsspam
Feb 12 19:44:19 debian-2gb-nbg1-2 kernel: \[3792289.095985\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=77.247.108.14 DST=195.201.40.59 LEN=438 TOS=0x00 PREC=0x00 TTL=51 ID=0 DF PROTO=UDP SPT=5106 DPT=5060 LEN=418
2020-02-13 03:00:46
172.104.76.217 attack
firewall-block, port(s): 7777/tcp
2020-02-13 02:49:36
184.105.139.109 attackbots
30005/tcp 21/tcp 3389/tcp...
[2019-12-13/2020-02-12]31pkt,10pt.(tcp),3pt.(udp)
2020-02-13 03:11:14
49.88.112.116 attack
Failed password for root from 49.88.112.116 port 17949 ssh2
Failed password for root from 49.88.112.116 port 17949 ssh2
Failed password for root from 49.88.112.116 port 17949 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.116  user=root
Failed password for root from 49.88.112.116 port 16947 ssh2
2020-02-13 02:35:17
2a03:b0c0:1:e0::4db:d001 attackbots
(sshd) Failed SSH login from 2a03:b0c0:1:e0::4db:d001 (GB/United Kingdom/England/London/min-extra-grab-102-uk-prod.binaryedge.ninja/[AS14061 DigitalOcean, LLC]): 1 in the last 3600 secs
2020-02-13 02:49:15
221.146.233.140 attackbotsspam
Feb 12 16:47:42 MK-Soft-VM3 sshd[24055]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.146.233.140 
Feb 12 16:47:45 MK-Soft-VM3 sshd[24055]: Failed password for invalid user rosin from 221.146.233.140 port 50865 ssh2
...
2020-02-13 02:59:44
162.247.74.74 attack
Feb 12 10:41:57 ws24vmsma01 sshd[142357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.74.74
Feb 12 10:41:59 ws24vmsma01 sshd[142357]: Failed password for invalid user admin from 162.247.74.74 port 45588 ssh2
...
2020-02-13 03:02:35
106.12.43.142 attackbots
Feb 12 15:16:43 legacy sshd[2133]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.43.142
Feb 12 15:16:45 legacy sshd[2133]: Failed password for invalid user zhang from 106.12.43.142 port 43050 ssh2
Feb 12 15:21:20 legacy sshd[2343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.43.142
...
2020-02-13 02:54:15
92.63.194.105 attackbotsspam
Feb 12 20:02:30 vps691689 sshd[18925]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.105
Feb 12 20:02:32 vps691689 sshd[18925]: Failed password for invalid user admin from 92.63.194.105 port 41997 ssh2
...
2020-02-13 03:04:19
80.82.70.118 attackspam
Feb 12 19:46:23 debian-2gb-nbg1-2 kernel: \[3792412.661441\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.70.118 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=41800 PROTO=TCP SPT=60000 DPT=6889 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-13 03:11:37
178.34.163.202 attack
Feb 12 15:28:21 django sshd[119349]: Invalid user router from 178.34.163.202
Feb 12 15:28:22 django sshd[119349]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.34.163.202 
Feb 12 15:28:24 django sshd[119349]: Failed password for invalid user router from 178.34.163.202 port 10444 ssh2
Feb 12 15:28:24 django sshd[119350]: Connection closed by 178.34.163.202
Feb 12 15:28:31 django sshd[119359]: Invalid user router from 178.34.163.202
Feb 12 15:28:31 django sshd[119359]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.34.163.202 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=178.34.163.202
2020-02-13 02:24:50
35.206.156.221 attackspambots
Feb 12 18:47:16 markkoudstaal sshd[13401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.206.156.221
Feb 12 18:47:18 markkoudstaal sshd[13401]: Failed password for invalid user jupyter from 35.206.156.221 port 39662 ssh2
Feb 12 18:50:23 markkoudstaal sshd[13950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.206.156.221
2020-02-13 02:24:28
113.54.156.52 attack
SSH login attempts brute force.
2020-02-13 02:35:55
186.251.55.190 attackspambots
Caught in portsentry honeypot
2020-02-13 02:32:41

Recently Reported IPs

139.5.31.208 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 139.5.36.244 139.5.36.47 139.5.36.246