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

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

;; QUESTION SECTION:
;34.126.114.242.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 19:56:51 CST 2025
;; MSG SIZE  rcvd: 107
Host info
242.114.126.34.in-addr.arpa domain name pointer 242.114.126.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
192.185.219.16 attackspam
(mod_security) mod_security (id:5000135) triggered by 192.185.219.16 (US/United States/vps.totalmetrica.com): 10 in the last 3600 secs; ID: zul
2020-06-24 01:44:07
49.233.145.188 attackbots
Jun 23 22:23:59 dhoomketu sshd[988456]: Invalid user festival from 49.233.145.188 port 45126
Jun 23 22:23:59 dhoomketu sshd[988456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.145.188 
Jun 23 22:23:59 dhoomketu sshd[988456]: Invalid user festival from 49.233.145.188 port 45126
Jun 23 22:24:01 dhoomketu sshd[988456]: Failed password for invalid user festival from 49.233.145.188 port 45126 ssh2
Jun 23 22:27:36 dhoomketu sshd[988507]: Invalid user tianyu from 49.233.145.188 port 56012
...
2020-06-24 01:15:23
144.217.207.24 attackspam
Unauthorized connection attempt detected from IP address 144.217.207.24 to port 8443 [T]
2020-06-24 01:49:05
194.1.232.158 attack
Unauthorized connection attempt detected from IP address 194.1.232.158 to port 445 [T]
2020-06-24 01:42:38
178.248.87.132 attack
20/6/23@11:54:11: FAIL: IoT-Telnet address from=178.248.87.132
...
2020-06-24 01:26:00
192.241.211.15 attack
 TCP (SYN) 192.241.211.15:39124 -> port 5984, len 44
2020-06-24 01:21:48
217.64.135.204 attackspambots
Unauthorized connection attempt detected from IP address 217.64.135.204 to port 23 [T]
2020-06-24 01:19:25
212.92.123.35 attack
Unauthorized connection attempt detected from IP address 212.92.123.35 to port 3389 [T]
2020-06-24 01:41:07
118.69.72.198 attackspambots
Unauthorized connection attempt detected from IP address 118.69.72.198 to port 445 [T]
2020-06-24 01:31:54
192.241.204.225 attack
Unauthorized connection attempt detected from IP address 192.241.204.225 to port 8081 [T]
2020-06-24 01:43:44
77.91.88.51 attack
Unauthorized connection attempt detected from IP address 77.91.88.51 to port 23 [T]
2020-06-24 01:38:01
178.217.168.84 attackspambots
1433/tcp 445/tcp...
[2020-04-25/06-23]12pkt,2pt.(tcp)
2020-06-24 01:46:42
177.67.75.34 attackspambots
Automatic report - Port Scan Attack
2020-06-24 01:47:11
128.14.209.234 attack
Unauthorized connection attempt detected from IP address 128.14.209.234 to port 443 [T]
2020-06-24 01:50:22
103.219.43.98 attackspambots
Unauthorized connection attempt detected from IP address 103.219.43.98 to port 445 [T]
2020-06-24 01:34:52

Recently Reported IPs

163.159.238.215 235.216.38.56 119.166.149.190 153.104.70.202
170.218.246.1 57.100.253.45 188.110.66.70 223.152.163.51
62.150.207.158 174.240.204.24 51.255.143.211 91.194.240.212
156.50.98.164 240.179.131.233 252.240.112.226 7.167.206.23
15.196.173.30 125.222.218.68 198.56.40.243 203.255.156.176