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.98.244 attack
 TCP (SYN) 139.162.98.244:57816 -> port 8118, len 44
2020-09-17 01:58:21
139.162.98.244 attack
Port Scan
...
2020-09-16 18:14:48
139.162.98.244 attackspambots
 TCP (SYN) 139.162.98.244:59055 -> port 8118, len 44
2020-08-13 04:50:58
139.162.98.244 attack
8118/tcp 8118/tcp 8118/tcp...
[2020-05-11/07-11]62pkt,1pt.(tcp)
2020-07-11 09:17:22
139.162.98.244 attack
Port 8118 scan denied
2020-04-08 13:54:18
139.162.98.244 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-06 03:14:03
139.162.98.244 attackbotsspam
unauthorized connection attempt
2020-02-04 13:28:33
139.162.98.244 attackbots
" "
2020-01-02 08:22:18
139.162.98.244 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-18 06:16:26
139.162.98.244 attack
firewall-block, port(s): 8118/tcp
2019-10-31 16:55:26
139.162.98.244 attackspambots
firewall-block, port(s): 8118/tcp
2019-10-27 00:10:23
139.162.98.244 attackspambots
" "
2019-09-29 23:52:45
139.162.98.244 attack
firewall-block, port(s): 8118/tcp
2019-09-26 09:10:30
139.162.98.244 attack
8118/tcp 8118/tcp 8118/tcp...
[2019-05-19/07-19]78pkt,1pt.(tcp)
2019-07-20 02:02:06
139.162.98.244 attackbotsspam
" "
2019-07-05 14:44:06
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.98.19
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1388
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.98.19.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:01:59 CST 2022
;; MSG SIZE  rcvd: 106
Host info
19.98.162.139.in-addr.arpa domain name pointer li1582-19.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
19.98.162.139.in-addr.arpa	name = li1582-19.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.31.204 attack
Jan  2 10:28:31 OPSO sshd\[22018\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.204  user=root
Jan  2 10:28:33 OPSO sshd\[22018\]: Failed password for root from 222.186.31.204 port 59752 ssh2
Jan  2 10:28:35 OPSO sshd\[22018\]: Failed password for root from 222.186.31.204 port 59752 ssh2
Jan  2 10:28:35 OPSO sshd\[22020\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.204  user=root
Jan  2 10:28:38 OPSO sshd\[22018\]: Failed password for root from 222.186.31.204 port 59752 ssh2
Jan  2 10:28:38 OPSO sshd\[22020\]: Failed password for root from 222.186.31.204 port 43721 ssh2
2020-01-02 17:38:21
212.22.79.241 attackspam
[portscan] Port scan
2020-01-02 17:54:13
148.255.174.229 attackbots
Jan  2 07:55:24 IngegnereFirenze sshd[24363]: Did not receive identification string from 148.255.174.229 port 35809
...
2020-01-02 17:34:03
218.92.0.175 attack
frenzy
2020-01-02 17:53:33
34.215.122.24 attackspam
01/02/2020-10:49:52.258217 34.215.122.24 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-02 18:03:22
212.112.98.146 attackbotsspam
Jan  2 07:26:46 tuxlinux sshd[36715]: Invalid user yangmin from 212.112.98.146 port 8341
Jan  2 07:26:46 tuxlinux sshd[36715]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.112.98.146 
Jan  2 07:26:46 tuxlinux sshd[36715]: Invalid user yangmin from 212.112.98.146 port 8341
Jan  2 07:26:46 tuxlinux sshd[36715]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.112.98.146 
...
2020-01-02 17:51:34
49.34.42.9 attackbots
Unauthorized connection attempt detected from IP address 49.34.42.9 to port 445
2020-01-02 17:40:24
210.16.189.19 attackbots
C2,WP GET /wp-login.php
2020-01-02 17:47:30
194.36.190.150 attack
Jan  2 10:31:50 silence02 sshd[26792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.36.190.150
Jan  2 10:31:52 silence02 sshd[26792]: Failed password for invalid user wwwrun from 194.36.190.150 port 39800 ssh2
Jan  2 10:33:35 silence02 sshd[26858]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.36.190.150
2020-01-02 17:49:29
95.178.159.193 attackbotsspam
Telnetd brute force attack detected by fail2ban
2020-01-02 17:32:06
61.93.201.198 attack
$f2bV_matches
2020-01-02 17:50:12
71.7.3.35 attack
Honeypot attack, port: 445, PTR: mtzm-static-01-0003.dsl.iowatelecom.net.
2020-01-02 17:43:26
94.103.232.253 attackspambots
[portscan] Port scan
2020-01-02 17:53:53
86.59.220.126 attackspam
Dec 31 20:28:12 mailrelay sshd[806]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.59.220.126  user=mysql
Dec 31 20:28:14 mailrelay sshd[806]: Failed password for mysql from 86.59.220.126 port 44565 ssh2
Dec 31 20:28:14 mailrelay sshd[806]: Received disconnect from 86.59.220.126 port 44565:11: Bye Bye [preauth]
Dec 31 20:28:14 mailrelay sshd[806]: Disconnected from 86.59.220.126 port 44565 [preauth]
Dec 31 20:36:02 mailrelay sshd[877]: Invalid user absolute from 86.59.220.126 port 45890
Dec 31 20:36:02 mailrelay sshd[877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.59.220.126
Dec 31 20:36:04 mailrelay sshd[877]: Failed password for invalid user absolute from 86.59.220.126 port 45890 ssh2
Dec 31 20:36:04 mailrelay sshd[877]: Received disconnect from 86.59.220.126 port 45890:11: Bye Bye [preauth]
Dec 31 20:36:04 mailrelay sshd[877]: Disconnected from 86.59.220.126 port 45890 [prea........
-------------------------------
2020-01-02 17:44:58
110.44.236.131 attackspam
Honeypot attack, port: 23, PTR: PTR record not found
2020-01-02 17:46:45

Recently Reported IPs

139.162.96.61 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 139.173.72.146 139.177.178.175
139.177.177.23 139.177.183.171 139.177.179.240 139.177.188.16
139.177.189.62 139.177.194.4 139.177.196.132 139.177.200.185