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: United States of America (the)

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

;; QUESTION SECTION:
;172.58.142.122.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 14:40:35 CST 2025
;; MSG SIZE  rcvd: 107
Host info
b'Host 122.142.58.172.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 122.142.58.172.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
159.192.96.253 attackbotsspam
SSH Brute Force
2019-11-09 01:26:06
167.58.65.38 attack
Brute force attempt
2019-11-09 01:26:38
171.6.191.125 attackspambots
Nov  8 20:00:00 server sshd\[11019\]: Invalid user dncin from 171.6.191.125
Nov  8 20:00:00 server sshd\[11019\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mx-ll-171.6.191-125.dynamic.3bb.co.th 
Nov  8 20:00:02 server sshd\[11019\]: Failed password for invalid user dncin from 171.6.191.125 port 5686 ssh2
Nov  8 20:09:22 server sshd\[13579\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mx-ll-171.6.191-125.dynamic.3bb.co.th  user=root
Nov  8 20:09:25 server sshd\[13579\]: Failed password for root from 171.6.191.125 port 6768 ssh2
...
2019-11-09 01:12:27
175.175.64.66 attackspam
Fail2Ban Ban Triggered
2019-11-09 01:21:12
185.9.84.182 attack
postfix
2019-11-09 01:51:43
34.67.110.131 attackbotsspam
34.67.110.131 - - [08/Nov/2019:11:37:32 -0300] "GET /Habbo/Comet-Server/commit/1309230b5fccb443d963ec39e244dec3269a2740?lang=es-ES%20or%20(1,2)=(select*from(select%20name_const(CHAR(111,108,111,108,111,115,104,101,114),1),name_const(CHAR(111,108,111,108,111,115,104,101,114),1))a)%20--%20and%201%3D1 HTTP/1.1" 200 106764 "-" "-"
34.67.110.131 - - [08/Nov/2019:11:37:33 -0300] "GET /Habbo/Comet-Server/commit/1309230b5fccb443d963ec39e244dec3269a2740?lang=es-ES%27%20or%20(1,2)=(select*from(select%20name_const(CHAR(111,108,111,108,111,115,104,101,114),1),name_const(CHAR(111,108,111,108,111,115,104,101,114),1))a)%20--%20%27x%27=%27x HTTP/1.1" 200 106757 "-" "-"
...
2019-11-09 01:49:15
45.89.106.160 attackspam
Connection by 45.89.106.160 on port: 9000 got caught by honeypot at 11/8/2019 1:38:08 PM
2019-11-09 01:33:19
211.144.122.42 attackspambots
Nov  8 18:02:54 mail sshd\[17427\]: Invalid user admin$123g from 211.144.122.42
Nov  8 18:02:54 mail sshd\[17427\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.144.122.42
Nov  8 18:02:57 mail sshd\[17427\]: Failed password for invalid user admin$123g from 211.144.122.42 port 46894 ssh2
...
2019-11-09 01:18:48
40.71.190.223 attackspambots
RDP Bruteforce
2019-11-09 01:25:34
167.114.231.174 attack
Nov  8 17:34:39 localhost sshd\[4440\]: Invalid user rh from 167.114.231.174 port 38338
Nov  8 17:34:39 localhost sshd\[4440\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.231.174
Nov  8 17:34:41 localhost sshd\[4440\]: Failed password for invalid user rh from 167.114.231.174 port 38338 ssh2
Nov  8 17:44:39 localhost sshd\[4729\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.231.174  user=root
Nov  8 17:44:42 localhost sshd\[4729\]: Failed password for root from 167.114.231.174 port 48178 ssh2
...
2019-11-09 01:48:34
223.171.46.146 attackspam
Nov  8 17:51:53 markkoudstaal sshd[2693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.171.46.146
Nov  8 17:51:55 markkoudstaal sshd[2693]: Failed password for invalid user ci from 223.171.46.146 port 63224 ssh2
Nov  8 17:56:22 markkoudstaal sshd[3008]: Failed password for root from 223.171.46.146 port 63224 ssh2
2019-11-09 01:12:02
196.35.41.86 attackspam
Nov  8 16:41:17 vpn01 sshd[10263]: Failed password for root from 196.35.41.86 port 52739 ssh2
Nov  8 16:46:10 vpn01 sshd[10418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.35.41.86
...
2019-11-09 01:17:06
148.70.138.31 attack
Nov  8 18:20:06 cp sshd[3712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.138.31
2019-11-09 01:29:01
103.75.101.23 attackspambots
Nov  8 16:24:28 XXX sshd[31845]: Invalid user matex from 103.75.101.23 port 7176
2019-11-09 01:45:46
201.47.158.130 attack
Nov  8 17:25:12 server sshd\[2683\]: Invalid user nitish from 201.47.158.130
Nov  8 17:25:12 server sshd\[2683\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.47.158.130 
Nov  8 17:25:14 server sshd\[2683\]: Failed password for invalid user nitish from 201.47.158.130 port 42898 ssh2
Nov  8 17:37:49 server sshd\[5637\]: Invalid user administrador from 201.47.158.130
Nov  8 17:37:49 server sshd\[5637\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.47.158.130 
...
2019-11-09 01:44:11

Recently Reported IPs

186.25.221.188 123.30.239.1 235.77.113.241 153.208.173.218
90.107.3.157 82.89.22.47 250.220.47.144 65.177.5.93
137.164.158.0 229.119.188.193 213.0.202.155 163.143.239.41
45.154.56.1 80.50.110.209 214.167.181.70 187.237.165.42
230.214.163.225 87.47.157.147 217.72.58.33 53.15.19.65