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

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

;; QUESTION SECTION:
;50.21.141.168.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 21 13:11:15 CST 2022
;; MSG SIZE  rcvd: 106
Host info
168.141.21.50.in-addr.arpa domain name pointer ip-50-21-141-168.dsl.netrevolution.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
168.141.21.50.in-addr.arpa	name = ip-50-21-141-168.dsl.netrevolution.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
219.78.206.158 attackspambots
Honeypot attack, port: 5555, PTR: n219078206158.netvigator.com.
2020-03-07 03:38:39
108.243.112.12 attackbotsspam
Scan detected and blocked 2020.03.06 14:29:00
2020-03-07 03:47:27
78.164.180.144 attackspam
Mar  6 14:29:14 debian-2gb-nbg1-2 kernel: \[5760519.275592\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=78.164.180.144 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=TCP SPT=44352 DPT=443 WINDOW=0 RES=0x00 RST URGP=0 
Mar  6 14:29:14 debian-2gb-nbg1-2 kernel: \[5760519.307265\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=78.164.180.144 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=TCP SPT=44352 DPT=443 WINDOW=0 RES=0x00 RST URGP=0
2020-03-07 03:35:34
183.134.65.22 attack
suspicious action Fri, 06 Mar 2020 10:28:40 -0300
2020-03-07 04:02:50
49.144.13.144 attackspam
Honeypot attack, port: 445, PTR: dsl.49.144.13.144.pldt.net.
2020-03-07 04:01:27
218.89.61.40 attackspam
Unauthorised access (Mar  6) SRC=218.89.61.40 LEN=40 TTL=242 ID=29184 TCP DPT=1433 WINDOW=1024 SYN
2020-03-07 04:11:13
91.196.36.246 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-07 03:41:28
106.13.74.82 attackbotsspam
Mar  6 18:02:19 vserver sshd\[7271\]: Invalid user robert from 106.13.74.82Mar  6 18:02:21 vserver sshd\[7271\]: Failed password for invalid user robert from 106.13.74.82 port 38066 ssh2Mar  6 18:10:12 vserver sshd\[7378\]: Invalid user aws from 106.13.74.82Mar  6 18:10:14 vserver sshd\[7378\]: Failed password for invalid user aws from 106.13.74.82 port 40746 ssh2
...
2020-03-07 03:43:08
200.209.174.76 attackspam
Mar  6 05:55:23 hanapaa sshd\[28892\]: Invalid user P4SSW0RD2020 from 200.209.174.76
Mar  6 05:55:23 hanapaa sshd\[28892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
Mar  6 05:55:25 hanapaa sshd\[28892\]: Failed password for invalid user P4SSW0RD2020 from 200.209.174.76 port 50151 ssh2
Mar  6 06:00:39 hanapaa sshd\[29309\]: Invalid user ROOT1@3\$ from 200.209.174.76
Mar  6 06:00:39 hanapaa sshd\[29309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
2020-03-07 03:39:14
139.59.58.155 attackspam
Mar  6 15:46:30 ArkNodeAT sshd\[10827\]: Invalid user neutron from 139.59.58.155
Mar  6 15:46:30 ArkNodeAT sshd\[10827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.58.155
Mar  6 15:46:32 ArkNodeAT sshd\[10827\]: Failed password for invalid user neutron from 139.59.58.155 port 33614 ssh2
2020-03-07 04:03:39
196.38.70.24 attack
Invalid user apache from 196.38.70.24 port 18132
2020-03-07 03:43:35
136.232.8.34 attack
Unauthorized connection attempt from IP address 136.232.8.34 on Port 445(SMB)
2020-03-07 04:05:13
18.189.193.123 attackbotsspam
suspicious action Fri, 06 Mar 2020 10:28:37 -0300
2020-03-07 04:06:10
209.17.96.90 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 56f71fc52a78e3aa | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: lab.skk.moe | User-Agent: Mozilla/5.0 (compatible; Nimbostratus-Bot/v1.3.2; http://cloudsystemnetworks.com) | CF_DC: ATL. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2020-03-07 03:36:53
45.133.99.130 attack
Mar  6 20:22:29 relay postfix/smtpd\[18577\]: warning: unknown\[45.133.99.130\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  6 20:22:47 relay postfix/smtpd\[18025\]: warning: unknown\[45.133.99.130\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  6 20:25:30 relay postfix/smtpd\[18577\]: warning: unknown\[45.133.99.130\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  6 20:25:50 relay postfix/smtpd\[18392\]: warning: unknown\[45.133.99.130\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  6 20:36:24 relay postfix/smtpd\[18392\]: warning: unknown\[45.133.99.130\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-07 03:37:44

Recently Reported IPs

42.5.16.114 143.117.155.14 173.214.175.178 45.93.16.178
58.9.254.23 29.37.236.2 95.31.111.14 41.184.8.30
183.63.253.59 164.68.127.80 198.244.237.180 75.212.138.46
73.82.180.45 39.173.10.194 249.0.14.62 194.145.60.254
51.124.10.5 186.61.53.62 60.250.108.223 31.100.237.90