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

Region: California

Country: United States

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

;; QUESTION SECTION:
;142.129.33.239.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 08:09:56 CST 2025
;; MSG SIZE  rcvd: 107
Host info
239.33.129.142.in-addr.arpa domain name pointer syn-142-129-033-239.res.spectrum.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
239.33.129.142.in-addr.arpa	name = syn-142-129-033-239.res.spectrum.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
202.79.168.214 attack
Mar 29 11:56:31 XXX sshd[40226]: Invalid user pz from 202.79.168.214 port 34620
2020-03-29 20:12:18
23.21.213.140 attackspam
SSH login attempts.
2020-03-29 19:57:11
108.177.10.27 attack
SSH login attempts.
2020-03-29 19:45:37
164.132.193.27 attackspambots
fail2ban
2020-03-29 19:47:18
51.91.11.200 attack
Mar 29 10:55:33 mail sshd\[32021\]: Invalid user mn from 51.91.11.200
Mar 29 10:55:33 mail sshd\[32021\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.11.200
Mar 29 10:55:35 mail sshd\[32021\]: Failed password for invalid user mn from 51.91.11.200 port 60926 ssh2
...
2020-03-29 20:24:20
104.47.58.161 attackspambots
SSH login attempts.
2020-03-29 20:10:29
220.167.161.200 attack
DATE:2020-03-29 07:35:50, IP:220.167.161.200, PORT:ssh SSH brute force auth (docker-dc)
2020-03-29 19:53:47
104.47.32.36 attackspam
SSH login attempts.
2020-03-29 20:07:23
64.8.71.111 attack
SSH login attempts.
2020-03-29 20:14:11
159.89.207.146 attackbotsspam
Mar 29 09:16:09 ns382633 sshd\[28330\]: Invalid user rjc from 159.89.207.146 port 47112
Mar 29 09:16:09 ns382633 sshd\[28330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.207.146
Mar 29 09:16:11 ns382633 sshd\[28330\]: Failed password for invalid user rjc from 159.89.207.146 port 47112 ssh2
Mar 29 09:22:06 ns382633 sshd\[29298\]: Invalid user fsn from 159.89.207.146 port 41586
Mar 29 09:22:06 ns382633 sshd\[29298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.207.146
2020-03-29 20:04:34
184.73.165.106 attack
SSH login attempts.
2020-03-29 19:58:18
71.237.171.150 attackspam
Mar 29 12:06:12 vps647732 sshd[4612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.237.171.150
Mar 29 12:06:14 vps647732 sshd[4612]: Failed password for invalid user osborne from 71.237.171.150 port 39564 ssh2
...
2020-03-29 20:20:54
24.7.248.54 attackbots
Invalid user markm from 24.7.248.54 port 51726
2020-03-29 20:09:14
199.59.241.250 attackspam
SSH login attempts.
2020-03-29 19:59:34
165.22.17.48 attack
Scanning
2020-03-29 19:46:53

Recently Reported IPs

61.205.159.141 122.198.13.153 221.221.132.135 45.105.253.132
92.35.186.51 145.138.105.218 180.74.152.160 172.47.99.77
247.85.33.165 74.50.227.42 54.94.224.160 234.205.166.213
94.195.177.45 156.179.135.198 182.155.160.209 68.83.30.235
153.68.108.25 164.244.162.205 200.194.6.25 212.125.53.18