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

;; QUESTION SECTION:
;242.122.245.72.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 14:53:26 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 72.245.122.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 72.245.122.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
83.31.89.129 attackbots
Invalid user ad from 83.31.89.129 port 35437
2020-01-22 03:30:52
165.22.213.24 attackbotsspam
Unauthorized connection attempt detected from IP address 165.22.213.24 to port 2220 [J]
2020-01-22 03:20:48
13.59.63.22 attackbots
Malicious/Probing: /wp-login.php
2020-01-22 03:44:33
179.108.126.114 attack
Jan 21 20:08:28 legacy sshd[23485]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.108.126.114
Jan 21 20:08:30 legacy sshd[23485]: Failed password for invalid user user from 179.108.126.114 port 29824 ssh2
Jan 21 20:09:28 legacy sshd[23514]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.108.126.114
...
2020-01-22 03:35:50
50.56.194.164 attackbotsspam
1579611482 - 01/21/2020 13:58:02 Host: 50.56.194.164/50.56.194.164 Port: 445 TCP Blocked
2020-01-22 03:10:17
60.205.222.239 attackbots
FTP Brute-Force reported by Fail2Ban
2020-01-22 03:26:24
54.37.68.191 attackbots
Unauthorized connection attempt detected from IP address 54.37.68.191 to port 2220 [J]
2020-01-22 03:32:18
173.235.137.181 attack
Unauthorized connection attempt detected from IP address 173.235.137.181 to port 2220 [J]
2020-01-22 03:08:38
80.41.230.70 attackspambots
Repeated attempts against wp-login
2020-01-22 03:17:13
37.120.192.22 attackspambots
0,31-12/04 [bc01/m05] PostRequest-Spammer scoring: Dodoma
2020-01-22 03:06:14
118.69.174.108 attackbots
php WP PHPmyadamin ABUSE blocked for 12h
2020-01-22 03:44:06
106.12.182.1 attack
Unauthorized connection attempt detected from IP address 106.12.182.1 to port 2220 [J]
2020-01-22 03:39:18
222.186.175.23 attackspam
Unauthorized connection attempt detected from IP address 222.186.175.23 to port 22 [J]
2020-01-22 03:37:16
181.171.20.168 attackspambots
Invalid user rocky from 181.171.20.168 port 29031
2020-01-22 03:33:23
89.243.8.84 attackspam
Unauthorized connection attempt detected from IP address 89.243.8.84 to port 23 [J]
2020-01-22 03:27:39

Recently Reported IPs

48.172.161.109 84.239.253.219 193.100.206.147 233.77.7.115
46.5.173.6 190.114.13.137 7.144.145.207 28.211.18.179
76.135.217.168 59.58.123.147 29.46.248.112 196.150.85.192
27.181.56.17 87.109.51.13 35.71.21.187 93.18.22.55
27.181.68.76 236.217.163.212 127.101.95.13 30.71.79.244