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

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

;; QUESTION SECTION:
;168.182.242.127.		IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 10:12:17 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 127.242.182.168.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 127.242.182.168.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
134.209.97.61 attackbots
frenzy
2019-08-14 04:29:01
205.209.174.241 attackbots
Aug 13 20:26:05 h2177944 kernel: \[4044510.764309\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=205.209.174.241 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=107 ID=256 PROTO=TCP SPT=6000 DPT=8888 WINDOW=16384 RES=0x00 SYN URGP=0 
Aug 13 20:26:05 h2177944 kernel: \[4044510.765174\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=205.209.174.241 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=107 ID=256 PROTO=TCP SPT=6000 DPT=7777 WINDOW=16384 RES=0x00 SYN URGP=0 
Aug 13 20:26:05 h2177944 kernel: \[4044510.765255\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=205.209.174.241 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=107 ID=256 PROTO=TCP SPT=6000 DPT=8080 WINDOW=16384 RES=0x00 SYN URGP=0 
Aug 13 20:26:05 h2177944 kernel: \[4044510.765274\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=205.209.174.241 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=107 ID=256 PROTO=TCP SPT=6000 DPT=8081 WINDOW=16384 RES=0x00 SYN URGP=0 
Aug 13 20:26:05 h2177944 kernel: \[4044510.765296\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=205.209.174.241 DST=85.214.117
2019-08-14 04:26:13
165.22.101.189 attackspambots
Aug 13 21:51:41 mout sshd[4009]: Invalid user marlon from 165.22.101.189 port 50806
2019-08-14 03:59:32
95.213.177.125 attackbotsspam
Port scan on 1 port(s): 8080
2019-08-14 03:49:55
119.205.220.98 attack
Aug 13 20:38:46 root sshd[5628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.205.220.98 
Aug 13 20:38:48 root sshd[5628]: Failed password for invalid user craig from 119.205.220.98 port 55200 ssh2
Aug 13 20:47:45 root sshd[5732]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.205.220.98 
...
2019-08-14 04:06:06
13.235.43.238 attackbotsspam
2019-08-13T18:26:02.257312abusebot.cloudsearch.cf sshd\[6249\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-13-235-43-238.ap-south-1.compute.amazonaws.com  user=root
2019-08-14 04:28:35
74.82.47.50 attackbots
873/tcp 9200/tcp 8080/tcp...
[2019-06-14/08-13]31pkt,15pt.(tcp),1pt.(udp)
2019-08-14 04:19:24
103.98.176.248 attackspambots
Aug 13 20:26:18 ks10 sshd[9401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.98.176.248 
Aug 13 20:26:20 ks10 sshd[9401]: Failed password for invalid user mahendra from 103.98.176.248 port 53814 ssh2
...
2019-08-14 04:17:50
77.42.73.119 attack
Automatic report - Port Scan Attack
2019-08-14 04:17:02
40.68.153.124 attack
2019-08-13T19:49:39.999375abusebot.cloudsearch.cf sshd\[7241\]: Invalid user ryan from 40.68.153.124 port 53642
2019-08-14 04:08:17
107.175.194.181 attackbots
$f2bV_matches
2019-08-14 04:14:02
192.187.98.254 attackspambots
[portscan] Port scan
2019-08-14 04:16:28
27.150.169.223 attack
$f2bV_matches
2019-08-14 03:46:33
198.108.67.42 attackspambots
" "
2019-08-14 03:53:19
187.109.10.100 attack
Multiple SSH auth failures recorded by fail2ban
2019-08-14 03:47:53

Recently Reported IPs

168.181.107.6 168.194.176.198 168.194.86.130 168.194.78.213
168.194.36.92 168.194.236.157 168.196.1.161 168.195.98.86
168.196.154.111 168.196.201.176 168.195.51.41 168.196.246.164
168.196.84.218 168.197.104.251 168.196.89.74 168.196.208.207
168.196.246.50 168.205.110.130 168.197.61.211 168.197.153.138