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

;; QUESTION SECTION:
;34.142.140.168.			IN	A

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

;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 08:30:36 CST 2025
;; MSG SIZE  rcvd: 107
Host info
168.140.142.34.in-addr.arpa domain name pointer 168.140.142.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
80.232.246.116 attackbots
Unauthorized connection attempt detected from IP address 80.232.246.116 to port 2220 [J]
2020-02-05 18:20:09
119.229.164.163 attackspam
Unauthorized connection attempt detected from IP address 119.229.164.163 to port 23 [J]
2020-02-05 18:14:13
222.223.236.76 attack
Unauthorized connection attempt detected from IP address 222.223.236.76 to port 1433 [J]
2020-02-05 18:05:26
89.38.184.152 attackspambots
Unauthorized connection attempt detected from IP address 89.38.184.152 to port 23 [J]
2020-02-05 18:18:53
106.54.141.8 attack
Unauthorized connection attempt detected from IP address 106.54.141.8 to port 2220 [J]
2020-02-05 17:53:29
189.140.137.99 attackbots
Unauthorized connection attempt detected from IP address 189.140.137.99 to port 80 [J]
2020-02-05 18:10:03
182.191.92.206 attackspam
Unauthorized connection attempt detected from IP address 182.191.92.206 to port 80 [J]
2020-02-05 18:11:11
81.248.2.197 attackbotsspam
Unauthorized connection attempt detected from IP address 81.248.2.197 to port 81 [J]
2020-02-05 17:57:06
77.139.119.252 attackbotsspam
Unauthorized connection attempt detected from IP address 77.139.119.252 to port 23 [J]
2020-02-05 18:20:38
36.80.40.72 attack
Unauthorized connection attempt detected from IP address 36.80.40.72 to port 80 [J]
2020-02-05 18:02:33
111.199.19.148 attackbotsspam
Unauthorized connection attempt detected from IP address 111.199.19.148 to port 2220 [J]
2020-02-05 18:15:10
43.228.65.43 attack
Unauthorized connection attempt detected from IP address 43.228.65.43 to port 1433 [J]
2020-02-05 18:00:34
177.170.142.2 attackspambots
Unauthorized connection attempt detected from IP address 177.170.142.2 to port 23 [J]
2020-02-05 18:11:42
170.79.171.68 attack
Unauthorized connection attempt detected from IP address 170.79.171.68 to port 2323 [J]
2020-02-05 18:12:49
14.29.215.69 attack
Feb  5 05:29:15 roki sshd[6979]: Invalid user bi from 14.29.215.69
Feb  5 05:29:15 roki sshd[6979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.29.215.69
Feb  5 05:29:17 roki sshd[6979]: Failed password for invalid user bi from 14.29.215.69 port 34606 ssh2
Feb  5 05:56:24 roki sshd[9908]: Invalid user spring from 14.29.215.69
Feb  5 05:56:24 roki sshd[9908]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.29.215.69
...
2020-02-05 18:26:19

Recently Reported IPs

134.107.149.101 101.128.78.37 15.184.108.17 180.146.168.100
255.68.132.165 192.182.252.20 88.138.138.155 219.18.247.39
193.59.179.1 119.252.6.160 238.0.190.104 132.23.119.127
202.201.122.189 188.12.220.80 72.99.203.198 221.201.125.233
120.55.205.119 156.95.159.131 170.219.35.129 73.64.74.16