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

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

;; QUESTION SECTION:
;53.152.241.142.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 20:52:18 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 142.241.152.53.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 142.241.152.53.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
118.193.21.186 attack
5432/tcp 3389/tcp...
[2019-11-03/12-22]19pkt,2pt.(tcp)
2019-12-24 04:08:09
124.115.106.150 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 03:58:15
103.238.213.158 attack
3389/tcp 3389/tcp 3389/tcp
[2019-12-18/22]3pkt
2019-12-24 04:06:11
112.196.169.126 attackspam
Dec 23 05:34:56 hanapaa sshd\[7432\]: Invalid user santorum from 112.196.169.126
Dec 23 05:34:56 hanapaa sshd\[7432\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.196.169.126
Dec 23 05:34:58 hanapaa sshd\[7432\]: Failed password for invalid user santorum from 112.196.169.126 port 36917 ssh2
Dec 23 05:44:03 hanapaa sshd\[8274\]: Invalid user datoo from 112.196.169.126
Dec 23 05:44:03 hanapaa sshd\[8274\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.196.169.126
2019-12-24 03:41:54
129.204.38.136 attackbots
Apr 19 12:26:32 yesfletchmain sshd\[22856\]: Invalid user nr from 129.204.38.136 port 38920
Apr 19 12:26:32 yesfletchmain sshd\[22856\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.38.136
Apr 19 12:26:34 yesfletchmain sshd\[22856\]: Failed password for invalid user nr from 129.204.38.136 port 38920 ssh2
Apr 19 12:30:32 yesfletchmain sshd\[23152\]: Invalid user desktop from 129.204.38.136 port 37330
Apr 19 12:30:32 yesfletchmain sshd\[23152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.38.136
...
2019-12-24 03:43:02
178.128.150.158 attackbots
Dec 23 15:55:33 MK-Soft-VM4 sshd[9178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.150.158 
Dec 23 15:55:35 MK-Soft-VM4 sshd[9178]: Failed password for invalid user s91 from 178.128.150.158 port 41918 ssh2
...
2019-12-24 03:53:52
202.88.246.161 attackbotsspam
Dec 23 16:29:41 markkoudstaal sshd[20656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.88.246.161
Dec 23 16:29:43 markkoudstaal sshd[20656]: Failed password for invalid user prats from 202.88.246.161 port 56629 ssh2
Dec 23 16:36:34 markkoudstaal sshd[21204]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.88.246.161
2019-12-24 03:48:29
170.80.49.2 attackspam
1433/tcp 445/tcp...
[2019-10-23/12-22]16pkt,2pt.(tcp)
2019-12-24 04:03:55
129.204.29.45 attack
Feb 27 00:05:13 dillonfme sshd\[29048\]: Invalid user nw from 129.204.29.45 port 53996
Feb 27 00:05:13 dillonfme sshd\[29048\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.29.45
Feb 27 00:05:15 dillonfme sshd\[29048\]: Failed password for invalid user nw from 129.204.29.45 port 53996 ssh2
Feb 27 00:11:21 dillonfme sshd\[29306\]: User backup from 129.204.29.45 not allowed because not listed in AllowUsers
Feb 27 00:11:21 dillonfme sshd\[29306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.29.45  user=backup
...
2019-12-24 03:49:42
129.204.241.31 attackbotsspam
Dec  8 18:18:23 yesfletchmain sshd\[3640\]: Invalid user terajima from 129.204.241.31 port 51094
Dec  8 18:18:23 yesfletchmain sshd\[3640\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.241.31
Dec  8 18:18:25 yesfletchmain sshd\[3640\]: Failed password for invalid user terajima from 129.204.241.31 port 51094 ssh2
Dec  8 18:25:13 yesfletchmain sshd\[4089\]: Invalid user yeaping from 129.204.241.31 port 58980
Dec  8 18:25:13 yesfletchmain sshd\[4089\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.241.31
...
2019-12-24 03:51:38
220.85.104.202 attack
Dec 23 05:45:15 wbs sshd\[445\]: Invalid user mfs from 220.85.104.202
Dec 23 05:45:15 wbs sshd\[445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.85.104.202
Dec 23 05:45:17 wbs sshd\[445\]: Failed password for invalid user mfs from 220.85.104.202 port 22995 ssh2
Dec 23 05:51:35 wbs sshd\[1104\]: Invalid user server from 220.85.104.202
Dec 23 05:51:35 wbs sshd\[1104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.85.104.202
2019-12-24 04:04:36
129.204.210.237 attackspam
Apr 24 10:29:28 yesfletchmain sshd\[19541\]: Invalid user sentry from 129.204.210.237 port 56464
Apr 24 10:29:28 yesfletchmain sshd\[19541\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.210.237
Apr 24 10:29:30 yesfletchmain sshd\[19541\]: Failed password for invalid user sentry from 129.204.210.237 port 56464 ssh2
Apr 24 10:32:11 yesfletchmain sshd\[19597\]: Invalid user amssys from 129.204.210.237 port 53262
Apr 24 10:32:11 yesfletchmain sshd\[19597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.210.237
...
2019-12-24 03:59:19
178.164.140.196 attack
1577112948 - 12/23/2019 15:55:48 Host: 178.164.140.196/178.164.140.196 Port: 445 TCP Blocked
2019-12-24 03:38:12
117.34.118.44 attack
12/23/2019-20:15:54.286046 117.34.118.44 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-24 04:09:10
129.204.3.8 attackspam
May 22 17:59:14 yesfletchmain sshd\[24288\]: Invalid user ux from 129.204.3.8 port 33786
May 22 17:59:14 yesfletchmain sshd\[24288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.3.8
May 22 17:59:16 yesfletchmain sshd\[24288\]: Failed password for invalid user ux from 129.204.3.8 port 33786 ssh2
May 22 18:04:38 yesfletchmain sshd\[24393\]: Invalid user sun from 129.204.3.8 port 45772
May 22 18:04:38 yesfletchmain sshd\[24393\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.3.8
...
2019-12-24 03:47:42

Recently Reported IPs

245.144.27.255 174.75.168.101 27.201.166.183 16.236.31.215
163.128.13.197 116.188.239.214 202.90.131.37 217.235.113.157
188.132.137.148 82.6.78.77 230.113.138.167 124.219.119.164
78.157.109.57 250.251.32.72 56.101.159.212 82.42.44.142
146.250.156.224 230.21.39.97 154.249.239.43 39.6.144.11