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

;; QUESTION SECTION:
;242.164.222.126.		IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 16:47:07 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 126.222.164.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 126.222.164.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
115.159.214.247 attackbotsspam
Invalid user admin from 115.159.214.247 port 51930
2019-08-27 17:01:27
104.244.76.33 attackspambots
Caught in portsentry honeypot
2019-08-27 17:02:24
60.250.164.169 attack
Aug 27 14:41:09 areeb-Workstation sshd\[30869\]: Invalid user tomcat from 60.250.164.169
Aug 27 14:41:09 areeb-Workstation sshd\[30869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.250.164.169
Aug 27 14:41:11 areeb-Workstation sshd\[30869\]: Failed password for invalid user tomcat from 60.250.164.169 port 36268 ssh2
...
2019-08-27 17:12:19
122.14.209.213 attackspam
Aug 27 11:13:01 vps647732 sshd[16052]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.14.209.213
Aug 27 11:13:04 vps647732 sshd[16052]: Failed password for invalid user n from 122.14.209.213 port 43324 ssh2
...
2019-08-27 17:18:08
139.255.113.234 attackbots
Unauthorized connection attempt from IP address 139.255.113.234 on Port 445(SMB)
2019-08-27 16:59:55
203.162.13.68 attackspam
2019-08-27T09:40:28.056876abusebot-8.cloudsearch.cf sshd\[31926\]: Invalid user nj from 203.162.13.68 port 60010
2019-08-27 18:00:18
49.88.112.74 attack
2019-08-27T08:37:31.428437abusebot-6.cloudsearch.cf sshd\[25560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.74  user=root
2019-08-27 17:08:34
51.255.192.217 attackspam
$f2bV_matches
2019-08-27 17:04:29
139.59.85.59 attackspambots
Aug 27 09:10:17 marvibiene sshd[37265]: Invalid user garret from 139.59.85.59 port 35764
Aug 27 09:10:17 marvibiene sshd[37265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.85.59
Aug 27 09:10:17 marvibiene sshd[37265]: Invalid user garret from 139.59.85.59 port 35764
Aug 27 09:10:19 marvibiene sshd[37265]: Failed password for invalid user garret from 139.59.85.59 port 35764 ssh2
...
2019-08-27 17:27:25
175.173.194.173 attack
firewall-block, port(s): 23/tcp
2019-08-27 17:48:06
23.129.64.188 attackbotsspam
Reported by AbuseIPDB proxy server.
2019-08-27 17:26:26
109.129.218.5 attackbotsspam
$f2bV_matches
2019-08-27 17:03:28
106.12.176.146 attack
Aug 27 11:37:20 dedicated sshd[13532]: Invalid user awsjava from 106.12.176.146 port 36586
2019-08-27 17:57:13
189.135.123.222 attack
Automatic report - Port Scan Attack
2019-08-27 17:01:51
107.170.201.203 attack
firewall-block, port(s): 50908/tcp
2019-08-27 17:52:59

Recently Reported IPs

42.207.182.246 239.8.210.16 101.102.141.15 184.172.238.8
136.27.83.90 59.220.168.244 175.248.152.217 206.228.163.145
142.19.128.215 66.165.189.206 200.148.174.71 114.90.245.217
148.82.22.194 191.185.217.158 231.243.196.240 14.178.32.104
17.144.210.209 179.118.111.54 238.44.109.203 251.108.133.165