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

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

;; QUESTION SECTION:
;34.142.239.4.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 30 05:19:44 CST 2025
;; MSG SIZE  rcvd: 105
Host info
4.239.142.34.in-addr.arpa domain name pointer 4.239.142.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
4.239.142.34.in-addr.arpa	name = 4.239.142.34.bc.googleusercontent.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.226.118.137 attackbotsspam
Automatic report - SSH Brute-Force Attack
2020-01-14 09:18:34
125.231.130.150 attack
LGS,WP GET /wp-login.php
2020-01-14 08:55:53
123.207.78.83 attackspambots
Unauthorized connection attempt detected from IP address 123.207.78.83 to port 2220 [J]
2020-01-14 09:16:18
91.185.189.220 attack
Invalid user smtp from 91.185.189.220 port 51499
2020-01-14 08:58:36
51.15.101.80 attackspam
Unauthorized connection attempt detected from IP address 51.15.101.80 to port 2220 [J]
2020-01-14 09:05:30
124.236.47.59 attackspambots
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-01-14 09:03:01
114.119.150.142 attack
badbot
2020-01-14 09:12:10
222.186.30.76 attackbotsspam
01/13/2020-20:18:09.964946 222.186.30.76 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-14 09:21:59
212.85.91.19 attack
Unauthorized connection attempt detected from IP address 212.85.91.19 to port 23 [J]
2020-01-14 09:20:46
193.112.74.137 attack
Jan 14 00:40:52 mout sshd[25128]: Invalid user fuser from 193.112.74.137 port 48109
2020-01-14 09:15:22
183.251.175.73 attackbots
Port scan on 1 port(s): 21
2020-01-14 09:19:12
197.27.71.117 attackbots
Jan 14 00:44:28 raspberrypi sshd\[25473\]: Invalid user admin from 197.27.71.117 port 60747
Jan 14 00:44:29 raspberrypi sshd\[25477\]: Invalid user admin from 197.27.71.117 port 60853
Jan 14 00:44:30 raspberrypi sshd\[25481\]: Invalid user admin from 197.27.71.117 port 60998
...
2020-01-14 08:47:28
185.175.93.17 attackbots
01/13/2020-19:35:41.994980 185.175.93.17 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-01-14 08:48:31
114.119.155.37 attackspambots
badbot
2020-01-14 09:12:56
175.6.133.182 attack
Jan 14 01:03:53 [snip] postfix/smtpd[26734]: warning: unknown[175.6.133.182]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 14 01:04:00 [snip] postfix/smtpd[26734]: warning: unknown[175.6.133.182]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 14 01:04:11 [snip] postfix/smtpd[26734]: warning: unknown[175.6.133.182]: SASL LOGIN authentication failed: UGFzc3dvcmQ6[...]
2020-01-14 09:07:41

Recently Reported IPs

201.14.68.251 179.159.47.173 62.18.236.206 100.33.251.206
194.86.252.177 86.214.255.102 119.254.156.188 217.40.118.64
80.151.249.66 171.102.118.63 43.248.29.119 235.217.157.255
126.141.69.115 65.66.173.153 180.83.178.18 203.130.117.130
31.206.11.46 33.195.97.125 53.44.136.214 150.232.208.127