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

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.162.90.220 attack
" "
2020-07-26 07:20:22
139.162.90.220 attackspambots
 TCP (SYN) 139.162.90.220:57006 -> port 1723, len 44
2020-07-20 04:28:53
139.162.90.220 attack
firewall-block, port(s): 1723/tcp
2020-03-20 12:36:42
139.162.90.220 attackbotsspam
firewall-block, port(s): 1723/tcp
2020-03-19 10:00:29
139.162.90.220 attackbots
Portscan or hack attempt detected by psad/fwsnort
2020-02-28 07:37:04
139.162.90.220 attackspambots
Fail2Ban Ban Triggered
2020-02-25 04:24:52
139.162.90.220 attackspam
Port 1723 scan denied
2020-02-19 18:10:10
139.162.90.220 attack
" "
2020-02-15 01:02:57
139.162.90.220 attack
trying to access non-authorized port
2020-02-06 03:15:20
139.162.90.220 attackspam
firewall-block, port(s): 1723/tcp
2020-02-04 15:27:54
139.162.90.220 attackspambots
unauthorized connection attempt
2020-01-25 17:07:14
139.162.90.220 attack
" "
2020-01-09 07:07:05
139.162.90.220 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 04:51:02
139.162.90.220 attackspam
firewall-block, port(s): 1723/tcp
2019-12-17 02:35:48
139.162.90.220 attack
" "
2019-11-14 20:05:22
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.90.204
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34433
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.90.204.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:01:56 CST 2022
;; MSG SIZE  rcvd: 107
Host info
204.90.162.139.in-addr.arpa domain name pointer ps21j.lhtweb.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
204.90.162.139.in-addr.arpa	name = ps21j.lhtweb.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.86.78.88 attack
Trying ports that it shouldn't be.
2020-03-11 00:58:10
125.27.179.174 attack
(sshd) Failed SSH login from 125.27.179.174 (TH/Thailand/node-zhq.pool-125-27.dynamic.totinternet.net): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Mar 10 05:17:34 host sshd[99090]: Did not receive identification string from 125.27.179.174 port 56537
2020-03-11 01:28:18
113.179.34.173 attackbotsspam
1583831893 - 03/10/2020 10:18:13 Host: 113.179.34.173/113.179.34.173 Port: 445 TCP Blocked
2020-03-11 01:12:52
185.86.164.111 attackbots
Wordpress attack
2020-03-11 00:57:51
188.76.48.121 attack
Mar 10 16:10:46 ns382633 sshd\[10038\]: Invalid user pi from 188.76.48.121 port 16059
Mar 10 16:10:46 ns382633 sshd\[10038\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.76.48.121
Mar 10 16:10:46 ns382633 sshd\[10040\]: Invalid user pi from 188.76.48.121 port 16060
Mar 10 16:10:46 ns382633 sshd\[10040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.76.48.121
Mar 10 16:10:48 ns382633 sshd\[10038\]: Failed password for invalid user pi from 188.76.48.121 port 16059 ssh2
Mar 10 16:10:49 ns382633 sshd\[10040\]: Failed password for invalid user pi from 188.76.48.121 port 16060 ssh2
2020-03-11 01:20:10
117.5.254.78 attack
1583831917 - 03/10/2020 10:18:37 Host: 117.5.254.78/117.5.254.78 Port: 445 TCP Blocked
2020-03-11 00:59:19
222.124.185.123 attack
Automatic report - SSH Brute-Force Attack
2020-03-11 01:39:26
45.238.232.42 attackspambots
Tried sshing with brute force.
2020-03-11 01:38:54
122.179.163.251 attackbotsspam
SMB Server BruteForce Attack
2020-03-11 01:08:51
103.61.37.231 attackbots
Mar 10 16:14:03 ip-172-31-62-245 sshd\[9226\]: Invalid user minecraft from 103.61.37.231\
Mar 10 16:14:06 ip-172-31-62-245 sshd\[9226\]: Failed password for invalid user minecraft from 103.61.37.231 port 45655 ssh2\
Mar 10 16:18:35 ip-172-31-62-245 sshd\[9270\]: Invalid user fof from 103.61.37.231\
Mar 10 16:18:37 ip-172-31-62-245 sshd\[9270\]: Failed password for invalid user fof from 103.61.37.231 port 42885 ssh2\
Mar 10 16:21:52 ip-172-31-62-245 sshd\[9319\]: Invalid user uftp from 103.61.37.231\
2020-03-11 01:07:57
219.129.237.188 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-03-11 01:16:16
49.145.239.68 attackspambots
Unauthorized connection attempt from IP address 49.145.239.68 on Port 445(SMB)
2020-03-11 01:38:36
124.248.151.49 attack
POST /administrator/index.php HTTP/1.1 303 - Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
2020-03-11 01:14:04
120.29.226.10 attack
Mar 10 11:51:07 relay postfix/smtpd\[24818\]: warning: unknown\[120.29.226.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 10 11:52:29 relay postfix/smtpd\[24342\]: warning: unknown\[120.29.226.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 10 11:53:50 relay postfix/smtpd\[25465\]: warning: unknown\[120.29.226.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 10 12:00:41 relay postfix/smtpd\[25465\]: warning: unknown\[120.29.226.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 10 12:10:40 relay postfix/smtpd\[24342\]: warning: unknown\[120.29.226.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-11 00:53:15
180.183.193.151 attack
Port scan on 2 port(s): 8291 8728
2020-03-11 01:16:55

Recently Reported IPs

139.162.90.132 139.162.91.100 139.162.90.189 139.162.91.39
139.162.91.172 139.162.95.72 139.162.96.60 139.162.98.249
139.162.98.186 139.162.96.61 139.162.98.19 139.162.98.96
139.167.76.136 139.170.156.154 139.167.68.6 139.167.193.47
139.170.156.220 139.170.181.45 139.165.51.88 139.173.84.152