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: India

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

;; QUESTION SECTION:
;117.242.154.81.			IN	A

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

;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 20:43:05 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 81.154.242.117.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 81.154.242.117.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
82.64.15.106 attackspambots
Feb 12 23:55:18 mout sshd[18039]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.64.15.106  user=pi
Feb 12 23:55:20 mout sshd[18039]: Failed password for pi from 82.64.15.106 port 33718 ssh2
Feb 12 23:55:20 mout sshd[18039]: Connection closed by 82.64.15.106 port 33718 [preauth]
2020-02-13 07:09:35
103.78.137.54 attackspambots
port scan and connect, tcp 1433 (ms-sql-s)
2020-02-13 07:12:05
123.241.209.237 attack
firewall-block, port(s): 23/tcp
2020-02-13 07:01:07
185.175.93.101 attackspam
02/12/2020-18:08:39.759470 185.175.93.101 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-02-13 07:16:31
37.139.1.197 attackbots
Invalid user ceq from 37.139.1.197 port 53116
2020-02-13 06:59:56
189.253.174.14 attackspambots
1581545979 - 02/12/2020 23:19:39 Host: 189.253.174.14/189.253.174.14 Port: 445 TCP Blocked
2020-02-13 07:19:24
94.177.240.4 attackbots
Feb 12 12:43:56 auw2 sshd\[14554\]: Invalid user com from 94.177.240.4
Feb 12 12:43:56 auw2 sshd\[14554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.240.4
Feb 12 12:43:58 auw2 sshd\[14554\]: Failed password for invalid user com from 94.177.240.4 port 56540 ssh2
Feb 12 12:46:48 auw2 sshd\[14801\]: Invalid user valentin123 from 94.177.240.4
Feb 12 12:46:48 auw2 sshd\[14801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.240.4
2020-02-13 07:31:47
162.243.58.222 attackbots
$f2bV_matches
2020-02-13 07:02:41
106.13.78.180 attackbotsspam
Feb 12 23:20:00 srv206 sshd[23356]: Invalid user rolex from 106.13.78.180
Feb 12 23:20:00 srv206 sshd[23356]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.78.180
Feb 12 23:20:00 srv206 sshd[23356]: Invalid user rolex from 106.13.78.180
Feb 12 23:20:02 srv206 sshd[23356]: Failed password for invalid user rolex from 106.13.78.180 port 45088 ssh2
...
2020-02-13 07:06:27
194.26.29.124 attackbotsspam
Portscan or hack attempt detected by psad/fwsnort
2020-02-13 06:58:12
39.46.54.21 attack
Autoban   39.46.54.21 AUTH/CONNECT
2020-02-13 07:12:23
209.97.179.209 attack
Unauthorized connection attempt detected from IP address 209.97.179.209 to port 22
2020-02-13 07:30:00
163.172.71.191 attackbotsspam
RDP Bruteforce
2020-02-13 07:06:08
198.245.53.242 attack
Invalid user gzh from 198.245.53.242 port 60072
2020-02-13 07:13:13
45.125.66.89 attack
Rude login attack (4 tries in 1d)
2020-02-13 07:36:47

Recently Reported IPs

117.242.152.201 117.242.154.73 117.242.157.145 117.242.159.168
117.242.177.124 117.242.188.82 117.242.188.37 117.242.188.84
117.242.191.17 117.242.188.87 117.242.188.86 117.242.191.25
117.242.191.13 117.242.191.9 117.242.191.33 117.242.208.199
117.242.2.32 117.242.210.167 117.242.208.218 117.242.224.144