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: Frankfurt am Main

Region: Hesse

Country: Germany

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

;; QUESTION SECTION:
;139.162.156.36.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:07:21 CST 2022
;; MSG SIZE  rcvd: 107
Host info
36.156.162.139.in-addr.arpa domain name pointer li1423-36.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
36.156.162.139.in-addr.arpa	name = li1423-36.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
37.255.43.102 attack
Attempted connection to port 445.
2020-05-02 03:44:24
222.186.180.147 attack
May  1 21:37:15 legacy sshd[21715]: Failed password for root from 222.186.180.147 port 16744 ssh2
May  1 21:37:27 legacy sshd[21715]: error: maximum authentication attempts exceeded for root from 222.186.180.147 port 16744 ssh2 [preauth]
May  1 21:37:33 legacy sshd[21723]: Failed password for root from 222.186.180.147 port 17332 ssh2
...
2020-05-02 03:38:52
1.52.249.61 attack
Attempted connection to port 445.
2020-05-02 04:00:12
110.185.164.162 attackbots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-05-02 04:00:42
211.21.168.163 attackbots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-05-02 04:07:07
202.165.247.213 attack
20/5/1@14:21:57: FAIL: Alarm-Network address from=202.165.247.213
...
2020-05-02 03:39:17
131.161.224.12 attackspam
May  1 12:48:26 ip-172-31-62-245 sshd\[6017\]: Invalid user sinus from 131.161.224.12\
May  1 12:48:28 ip-172-31-62-245 sshd\[6017\]: Failed password for invalid user sinus from 131.161.224.12 port 45764 ssh2\
May  1 12:52:53 ip-172-31-62-245 sshd\[6162\]: Invalid user felipe from 131.161.224.12\
May  1 12:52:55 ip-172-31-62-245 sshd\[6162\]: Failed password for invalid user felipe from 131.161.224.12 port 58502 ssh2\
May  1 12:57:17 ip-172-31-62-245 sshd\[6210\]: Invalid user customer from 131.161.224.12\
2020-05-02 03:39:57
91.250.48.221 attackbots
Postfix RBL failed
2020-05-02 04:01:14
162.243.135.221 attackbotsspam
firewall-block, port(s): 137/udp
2020-05-02 03:51:54
78.175.224.175 attackspambots
Attempted connection to port 445.
2020-05-02 03:41:03
157.48.24.202 attackbotsspam
445/tcp
[2020-05-01]1pkt
2020-05-02 04:07:28
27.72.59.240 attackspambots
Unauthorized connection attempt from IP address 27.72.59.240 on Port 445(SMB)
2020-05-02 03:45:57
47.180.114.229 attackspam
May  1 21:58:57 mail sshd\[32693\]: Invalid user sylvia from 47.180.114.229
May  1 21:58:57 mail sshd\[32693\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.180.114.229
May  1 21:58:59 mail sshd\[32693\]: Failed password for invalid user sylvia from 47.180.114.229 port 41606 ssh2
...
2020-05-02 03:59:46
123.235.197.146 attackspam
Attempted connection to port 37215.
2020-05-02 03:52:24
162.243.136.81 attackbotsspam
9030/tcp
[2020-05-01]1pkt
2020-05-02 03:50:57

Recently Reported IPs

139.162.156.27 139.162.157.111 118.212.107.138 139.162.157.115
139.162.158.196 139.162.159.139 139.162.159.183 139.162.158.30
139.162.157.247 139.162.158.67 139.162.159.107 139.162.159.219
139.162.159.226 139.162.159.15 118.212.107.140 139.162.159.239
139.162.16.76 139.162.159.37 139.162.160.246 139.162.16.54