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

;; QUESTION SECTION:
;242.59.118.142.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 30 07:29:10 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 142.118.59.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 142.118.59.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
140.143.157.207 attack
Unauthorized connection attempt detected from IP address 140.143.157.207 to port 2220 [J]
2020-01-19 03:15:54
138.0.7.129 attackbots
Invalid user admin from 138.0.7.129 port 40582
2020-01-19 03:18:08
167.99.75.174 attack
Jan 18 20:03:17 s1 sshd\[18124\]: Invalid user dummy from 167.99.75.174 port 59688
Jan 18 20:03:17 s1 sshd\[18124\]: Failed password for invalid user dummy from 167.99.75.174 port 59688 ssh2
Jan 18 20:04:13 s1 sshd\[18175\]: Invalid user webmaster from 167.99.75.174 port 41470
Jan 18 20:04:13 s1 sshd\[18175\]: Failed password for invalid user webmaster from 167.99.75.174 port 41470 ssh2
Jan 18 20:05:12 s1 sshd\[18892\]: Invalid user postgres from 167.99.75.174 port 51506
Jan 18 20:05:12 s1 sshd\[18892\]: Failed password for invalid user postgres from 167.99.75.174 port 51506 ssh2
...
2020-01-19 03:10:51
192.144.137.208 attackbotsspam
Unauthorized connection attempt detected from IP address 192.144.137.208 to port 2220 [J]
2020-01-19 03:44:24
103.23.102.3 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2020-01-19 03:26:55
34.84.212.87 attack
Invalid user soporte from 34.84.212.87 port 52610
2020-01-19 03:36:59
220.88.1.208 attackbots
Unauthorized connection attempt detected from IP address 220.88.1.208 to port 2220 [J]
2020-01-19 03:38:28
111.229.31.134 attackspambots
Unauthorized connection attempt detected from IP address 111.229.31.134 to port 2220 [J]
2020-01-19 03:24:28
159.203.88.67 attackbots
Invalid user oracle from 159.203.88.67 port 42572
2020-01-19 03:12:33
64.190.91.254 attackspambots
Jan 18 19:41:13 sso sshd[1683]: Failed password for root from 64.190.91.254 port 36304 ssh2
...
2020-01-19 03:32:10
188.166.160.107 attack
Invalid user gilberto from 188.166.160.107 port 53706
2020-01-19 03:45:18
181.165.166.151 attackspambots
Invalid user lia from 181.165.166.151 port 41240
2020-01-19 03:47:23
124.193.199.202 attackbots
Invalid user admin from 124.193.199.202 port 33507
2020-01-19 03:20:53
156.196.19.72 attackbotsspam
Invalid user admin from 156.196.19.72 port 39861
2020-01-19 03:13:13
95.85.12.25 attack
Unauthorized connection attempt detected from IP address 95.85.12.25 to port 2220 [J]
2020-01-19 03:27:47

Recently Reported IPs

146.71.123.39 122.17.12.192 195.168.74.35 205.63.4.240
99.199.55.233 123.58.155.142 61.94.82.161 90.142.229.157
215.15.190.134 127.248.252.140 136.126.232.2 65.156.27.179
123.85.254.93 142.179.99.175 30.174.26.246 35.210.82.181
44.13.157.22 148.135.15.226 73.2.192.126 81.181.34.51