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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.162.222.196
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1495
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.162.222.196.		IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:36:56 CST 2022
;; MSG SIZE  rcvd: 108
Host info
196.222.162.139.in-addr.arpa domain name pointer li1385-196.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
196.222.162.139.in-addr.arpa	name = li1385-196.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.169.192 attackbotsspam
Jan 18 09:07:32 h2177944 sshd\[30219\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.192  user=root
Jan 18 09:07:34 h2177944 sshd\[30219\]: Failed password for root from 222.186.169.192 port 29202 ssh2
Jan 18 09:07:37 h2177944 sshd\[30219\]: Failed password for root from 222.186.169.192 port 29202 ssh2
Jan 18 09:07:40 h2177944 sshd\[30219\]: Failed password for root from 222.186.169.192 port 29202 ssh2
...
2020-01-18 16:21:12
107.181.174.74 attackbotsspam
Unauthorized connection attempt detected from IP address 107.181.174.74 to port 2220 [J]
2020-01-18 16:52:05
40.90.246.95 attackspam
Unauthorized connection attempt detected from IP address 40.90.246.95 to port 2220 [J]
2020-01-18 16:38:12
61.79.242.34 attackspambots
Unauthorized connection attempt detected from IP address 61.79.242.34 to port 4567 [J]
2020-01-18 16:35:20
222.136.148.122 attackbotsspam
Unauthorized connection attempt detected from IP address 222.136.148.122 to port 80 [T]
2020-01-18 16:39:04
42.113.73.250 attackbotsspam
Unauthorized connection attempt detected from IP address 42.113.73.250 to port 23 [J]
2020-01-18 16:37:27
124.156.55.67 attack
Unauthorized connection attempt detected from IP address 124.156.55.67 to port 5601 [J]
2020-01-18 16:29:33
106.52.159.188 attack
Unauthorized connection attempt detected from IP address 106.52.159.188 to port 2220 [J]
2020-01-18 16:30:35
103.242.2.16 attackbots
Unauthorized connection attempt detected from IP address 103.242.2.16 to port 2220 [J]
2020-01-18 16:53:58
98.203.87.59 attackspam
Unauthorized connection attempt detected from IP address 98.203.87.59 to port 81 [J]
2020-01-18 16:31:58
179.186.41.237 attackbots
Unauthorized connection attempt detected from IP address 179.186.41.237 to port 80 [J]
2020-01-18 16:45:39
103.102.30.66 attackspam
Unauthorized connection attempt detected from IP address 103.102.30.66 to port 8080 [J]
2020-01-18 16:31:26
37.123.207.224 attackspambots
Unauthorized connection attempt detected from IP address 37.123.207.224 to port 23 [J]
2020-01-18 16:17:29
93.155.162.13 attack
Unauthorized connection attempt detected from IP address 93.155.162.13 to port 8000 [J]
2020-01-18 16:55:42
109.121.167.32 attack
Unauthorized connection attempt detected from IP address 109.121.167.32 to port 8080 [J]
2020-01-18 16:51:39

Recently Reported IPs

139.162.219.5 139.162.221.11 139.162.223.183 139.162.222.111
139.162.226.211 139.162.224.17 139.162.225.109 139.162.225.65
139.162.226.71 139.162.226.63 139.162.228.212 139.162.23.221
139.162.229.221 139.162.228.14 139.162.231.37 139.162.231.99
139.162.231.11 139.162.234.62 139.162.234.120 139.162.234.61