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

;; QUESTION SECTION:
;240.180.134.242.		IN	A

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

;; Query time: 42 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 00:18:26 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 242.134.180.240.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 242.134.180.240.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
220.202.15.66 attackspambots
$f2bV_matches
2020-03-05 01:38:48
71.246.210.34 attack
$f2bV_matches
2020-03-05 01:51:19
201.150.255.185 attack
suspicious action Wed, 04 Mar 2020 10:35:10 -0300
2020-03-05 01:26:54
119.197.142.35 attackbotsspam
Honeypot attack, port: 5555, PTR: PTR record not found
2020-03-05 01:40:48
96.30.95.194 attackbotsspam
Honeypot attack, port: 445, PTR: static-96-30-95-194.violin.co.th.
2020-03-05 01:38:00
171.7.66.217 attackbotsspam
Honeypot attack, port: 81, PTR: mx-ll-171.7.66-217.dynamic.3bb.co.th.
2020-03-05 01:32:08
201.150.109.97 attack
suspicious action Wed, 04 Mar 2020 10:35:02 -0300
2020-03-05 01:36:08
201.241.232.203 attack
trying to access non-authorized port
2020-03-05 01:26:23
182.56.206.183 attackbotsspam
trying to access non-authorized port
2020-03-05 01:42:50
216.228.143.164 attackbots
Mar  4 18:12:52 sd-53420 sshd\[24097\]: Invalid user ubuntu from 216.228.143.164
Mar  4 18:12:52 sd-53420 sshd\[24097\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.228.143.164
Mar  4 18:12:54 sd-53420 sshd\[24097\]: Failed password for invalid user ubuntu from 216.228.143.164 port 58116 ssh2
Mar  4 18:21:02 sd-53420 sshd\[24810\]: Invalid user www1 from 216.228.143.164
Mar  4 18:21:02 sd-53420 sshd\[24810\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.228.143.164
...
2020-03-05 01:28:09
213.212.255.140 attackbots
frenzy
2020-03-05 02:07:32
220.167.100.60 attackspambots
Mar  4 09:35:11 NPSTNNYC01T sshd[29536]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.167.100.60
Mar  4 09:35:13 NPSTNNYC01T sshd[29536]: Failed password for invalid user test from 220.167.100.60 port 34140 ssh2
Mar  4 09:40:27 NPSTNNYC01T sshd[29766]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.167.100.60
...
2020-03-05 01:54:47
91.212.38.210 attackspambots
03/04/2020-10:36:09.099003 91.212.38.210 Protocol: 17 ET SCAN Sipvicious Scan
2020-03-05 01:36:56
193.112.1.26 attackspam
SSH Brute Force
2020-03-05 01:25:48
183.63.87.236 attackbots
Invalid user cisco from 183.63.87.236 port 35586
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.63.87.236
Failed password for invalid user cisco from 183.63.87.236 port 35586 ssh2
Invalid user usuario from 183.63.87.236 port 60402
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.63.87.236
2020-03-05 01:38:33

Recently Reported IPs

21.236.221.163 15.233.230.101 221.53.97.251 219.186.92.31
230.84.192.100 13.220.36.115 7.55.105.123 123.25.24.26
5.104.79.243 229.83.241.124 200.141.234.181 246.134.106.55
38.110.145.93 12.149.197.219 69.104.152.205 172.241.240.99
14.173.235.130 116.193.181.118 28.242.218.195 128.160.67.146