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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;242.129.246.114.		IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Aug 10 02:49:22 CST 2023
;; MSG SIZE  rcvd: 108
Host info
Host 114.246.129.242.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 114.246.129.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
93.174.93.46 attackspambots
19/6/30@09:29:19: FAIL: Alarm-Intrusion address from=93.174.93.46
...
2019-06-30 21:54:09
182.18.171.148 attackspambots
Jun 30 16:07:15 vpn01 sshd\[20351\]: Invalid user ftp from 182.18.171.148
Jun 30 16:07:15 vpn01 sshd\[20351\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.18.171.148
Jun 30 16:07:17 vpn01 sshd\[20351\]: Failed password for invalid user ftp from 182.18.171.148 port 60498 ssh2
2019-06-30 22:33:11
179.233.31.10 attackbotsspam
Jun 30 15:28:54 server sshd[17983]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.233.31.10
...
2019-06-30 22:03:29
139.99.166.240 attackspambots
xmlrpc attack
2019-06-30 21:57:44
121.152.165.213 attack
2019-06-30T20:26:58.891471enmeeting.mahidol.ac.th sshd\[6196\]: Invalid user admin from 121.152.165.213 port 2033
2019-06-30T20:26:58.907575enmeeting.mahidol.ac.th sshd\[6196\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.152.165.213
2019-06-30T20:27:00.686365enmeeting.mahidol.ac.th sshd\[6196\]: Failed password for invalid user admin from 121.152.165.213 port 2033 ssh2
...
2019-06-30 22:48:11
118.163.178.146 attackspambots
Jun 30 14:27:18 localhost sshd\[10554\]: Invalid user cron from 118.163.178.146 port 60393
Jun 30 14:27:18 localhost sshd\[10554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.163.178.146
...
2019-06-30 22:36:44
177.69.177.12 attackspambots
Jun 24 21:46:28 sanyalnet-cloud-vps3 sshd[5494]: Connection from 177.69.177.12 port 10400 on 45.62.248.66 port 22
Jun 24 21:46:30 sanyalnet-cloud-vps3 sshd[5494]: reveeclipse mapping checking getaddrinfo for 177-069-177-012.static.ctbctelecom.com.br [177.69.177.12] failed - POSSIBLE BREAK-IN ATTEMPT!
Jun 24 21:46:30 sanyalnet-cloud-vps3 sshd[5494]: Invalid user tcpdump from 177.69.177.12
Jun 24 21:46:30 sanyalnet-cloud-vps3 sshd[5494]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.69.177.12 
Jun 24 21:46:32 sanyalnet-cloud-vps3 sshd[5494]: Failed password for invalid user tcpdump from 177.69.177.12 port 10400 ssh2
Jun 24 21:46:32 sanyalnet-cloud-vps3 sshd[5494]: Received disconnect from 177.69.177.12: 11: Bye Bye [preauth]
Jun 24 21:50:16 sanyalnet-cloud-vps3 sshd[5590]: Connection from 177.69.177.12 port 10400 on 45.62.248.66 port 22
Jun 24 21:50:17 sanyalnet-cloud-vps3 sshd[5590]: reveeclipse mapping checking getaddrinfo f........
-------------------------------
2019-06-30 22:17:50
96.89.114.153 attackspam
RDP Bruteforce
2019-06-30 22:39:01
37.248.94.169 attack
19/6/30@09:27:23: FAIL: IoT-SSH address from=37.248.94.169
...
2019-06-30 22:35:56
36.189.253.226 attackspambots
Jun 30 15:59:28 s64-1 sshd[18553]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.189.253.226
Jun 30 15:59:30 s64-1 sshd[18553]: Failed password for invalid user docker from 36.189.253.226 port 32795 ssh2
Jun 30 16:03:40 s64-1 sshd[18578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.189.253.226
...
2019-06-30 22:21:45
176.130.149.145 attack
Jun 30 15:27:10 srv03 sshd\[25915\]: Invalid user adm from 176.130.149.145 port 54936
Jun 30 15:27:10 srv03 sshd\[25915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.130.149.145
Jun 30 15:27:12 srv03 sshd\[25915\]: Failed password for invalid user adm from 176.130.149.145 port 54936 ssh2
2019-06-30 22:40:10
126.227.205.97 attackspam
st-nyc1-01 recorded 3 login violations from 126.227.205.97 and was blocked at 2019-06-30 13:54:54. 126.227.205.97 has been blocked on 1 previous occasions. 126.227.205.97's first attempt was recorded at 2019-06-30 13:28:51
2019-06-30 22:05:31
85.201.213.223 attack
Jun 30 15:27:05 pornomens sshd\[2481\]: Invalid user admin2 from 85.201.213.223 port 20927
Jun 30 15:27:05 pornomens sshd\[2481\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.201.213.223
Jun 30 15:27:07 pornomens sshd\[2481\]: Failed password for invalid user admin2 from 85.201.213.223 port 20927 ssh2
...
2019-06-30 22:42:15
5.90.213.46 attack
Chat Spam
2019-06-30 21:58:07
110.145.126.98 attack
Microsoft-Windows-Security-Auditing
2019-06-30 21:59:07

Recently Reported IPs

132.147.202.74 155.111.148.119 217.91.231.254 71.140.13.210
174.85.233.112 213.233.110.203 222.10.96.11 36.82.98.152
63.95.240.158 77.220.32.242 183.253.225.247 95.111.194.65
57.199.245.218 39.108.187.166 181.46.164.19 181.143.201.80
186.143.201.80 186.143.202.234 186.141.136.155 165.22.253.245