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

;; QUESTION SECTION:
;242.42.241.18.			IN	A

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

;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 23:51:41 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 18.241.42.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 18.241.42.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
163.44.153.96 attackspambots
Invalid user jk from 163.44.153.96 port 7231
2020-04-01 16:20:52
64.225.1.4 attackspambots
Invalid user clp from 64.225.1.4 port 51706
2020-04-01 16:32:47
202.107.238.14 attackbots
Apr  1 06:34:14 ip-172-31-62-245 sshd\[5304\]: Invalid user pr from 202.107.238.14\
Apr  1 06:34:16 ip-172-31-62-245 sshd\[5304\]: Failed password for invalid user pr from 202.107.238.14 port 34183 ssh2\
Apr  1 06:37:29 ip-172-31-62-245 sshd\[5469\]: Invalid user fml from 202.107.238.14\
Apr  1 06:37:31 ip-172-31-62-245 sshd\[5469\]: Failed password for invalid user fml from 202.107.238.14 port 50974 ssh2\
Apr  1 06:40:56 ip-172-31-62-245 sshd\[5556\]: Failed password for root from 202.107.238.14 port 39524 ssh2\
2020-04-01 16:14:31
46.61.235.111 attackspam
$f2bV_matches
2020-04-01 16:06:40
67.207.88.161 attackbotsspam
$f2bV_matches
2020-04-01 15:57:41
34.69.73.10 attackspambots
Automatically reported by fail2ban report script (mx1)
2020-04-01 16:22:04
164.163.99.10 attack
Invalid user jk from 164.163.99.10 port 37882
2020-04-01 16:26:01
91.247.233.91 attackbotsspam
Port probing on unauthorized port 26
2020-04-01 15:49:13
142.93.140.242 attackbots
k+ssh-bruteforce
2020-04-01 16:34:36
66.181.164.159 attackbotsspam
Icarus honeypot on github
2020-04-01 16:23:00
167.71.219.32 attack
167.71.219.32 - - \[01/Apr/2020:04:03:16 +0200\] "POST /wp-login.php HTTP/1.1" 200 9691 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
167.71.219.32 - - \[01/Apr/2020:05:50:44 +0200\] "POST /wp-login.php HTTP/1.1" 200 9691 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
...
2020-04-01 16:37:15
148.70.223.115 attack
<6 unauthorized SSH connections
2020-04-01 16:05:15
45.64.126.103 attackspambots
SSH brute-force attempt
2020-04-01 16:27:11
164.155.127.115 attackbots
04/01/2020-03:53:41.542264 164.155.127.115 Protocol: 1 ET DROP Spamhaus DROP Listed Traffic Inbound group 16
2020-04-01 16:30:23
62.204.232.176 attack
scan z
2020-04-01 15:50:22

Recently Reported IPs

208.198.251.63 184.196.33.175 201.206.235.188 100.112.130.119
207.48.27.62 108.87.199.26 176.243.103.146 39.249.158.100
66.150.195.223 174.143.193.130 213.135.189.219 140.52.130.87
75.120.240.40 247.81.189.9 142.231.125.24 56.28.230.214
17.105.212.85 165.219.176.251 141.229.89.44 240.193.182.92