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

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

;; QUESTION SECTION:
;42.110.142.157.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 17:42:12 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 157.142.110.42.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 157.142.110.42.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
78.16.149.169 attackbots
Invalid user debug from 78.16.149.169 port 51258
2020-06-12 19:47:09
69.61.84.222 attackbots
[H1.VM8] Blocked by UFW
2020-06-12 19:31:41
160.20.166.59 attackbotsspam
" "
2020-06-12 19:32:29
188.86.177.182 attackspam
20/6/12@01:00:14: FAIL: Alarm-Network address from=188.86.177.182
20/6/12@01:00:14: FAIL: Alarm-Network address from=188.86.177.182
...
2020-06-12 19:45:03
164.132.42.32 attackspam
fail2ban -- 164.132.42.32
...
2020-06-12 19:52:28
112.84.94.148 attackbotsspam
spam (f2b h1)
2020-06-12 19:50:39
2605:6000:101c:86f9:dd5e:2736:5231:8a70 attackspambots
query suspecte, Sniffing for wordpress log:/2020/wp-login.php
2020-06-12 20:07:53
1.54.222.171 attackspam
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-06-12 19:33:21
180.76.37.36 attackbotsspam
 TCP (SYN) 180.76.37.36:46686 -> port 19237, len 44
2020-06-12 19:54:15
152.136.139.129 attackbotsspam
Jun 11 23:35:10 r.ca sshd[17331]: Failed password for root from 152.136.139.129 port 58676 ssh2
2020-06-12 19:48:39
177.33.31.96 attack
Invalid user wuchunpeng from 177.33.31.96 port 55974
2020-06-12 19:39:59
190.129.47.148 attackspambots
Invalid user xiaohui from 190.129.47.148 port 58143
2020-06-12 19:38:02
106.12.147.79 attackspambots
SSH Brute-Force Attack
2020-06-12 19:41:15
62.102.148.68 attackspam
Jun 12 11:23:22 web8 sshd\[25285\]: Invalid user USERID from 62.102.148.68
Jun 12 11:23:23 web8 sshd\[25285\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.102.148.68
Jun 12 11:23:25 web8 sshd\[25285\]: Failed password for invalid user USERID from 62.102.148.68 port 58782 ssh2
Jun 12 11:24:49 web8 sshd\[26065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.102.148.68  user=root
Jun 12 11:24:51 web8 sshd\[26065\]: Failed password for root from 62.102.148.68 port 39966 ssh2
2020-06-12 19:36:42
185.220.101.212 attackbotsspam
Jun 12 11:17:41 web8 sshd\[22005\]: Invalid user openelec from 185.220.101.212
Jun 12 11:17:41 web8 sshd\[22005\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.212
Jun 12 11:17:43 web8 sshd\[22005\]: Failed password for invalid user openelec from 185.220.101.212 port 18126 ssh2
Jun 12 11:22:01 web8 sshd\[24520\]: Invalid user leo from 185.220.101.212
Jun 12 11:22:02 web8 sshd\[24520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.212
2020-06-12 19:41:51

Recently Reported IPs

184.94.34.191 154.46.141.80 34.124.186.223 185.241.172.50
243.103.186.217 81.52.29.153 67.209.26.145 64.101.1.220
8.120.114.221 214.181.87.38 132.185.9.209 48.4.77.2
51.70.36.40 138.121.108.55 119.43.20.5 12.18.102.238
37.45.74.46 100.39.63.111 200.236.166.158 86.44.245.219