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

;; QUESTION SECTION:
;50.71.93.12.			IN	A

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

;; Query time: 42 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 13:18:36 CST 2025
;; MSG SIZE  rcvd: 104
Host info
12.93.71.50.in-addr.arpa domain name pointer S0106989d5df7b40f.wp.shawcable.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.93.71.50.in-addr.arpa	name = S0106989d5df7b40f.wp.shawcable.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.248.81.104 attackbots
02/01/2020-19:53:00.044748 104.248.81.104 Protocol: 6 ET CHAT IRC PING command
2020-02-02 04:52:54
222.186.52.139 attackbots
Unauthorized connection attempt detected from IP address 222.186.52.139 to port 22 [J]
2020-02-02 04:55:58
140.246.175.68 attack
Unauthorized connection attempt detected from IP address 140.246.175.68 to port 2220 [J]
2020-02-02 05:01:49
190.6.0.132 attackspambots
Honeypot attack, port: 445, PTR: docs-res-mbo-190-6-0-132.NET-UNO.NET.
2020-02-02 04:43:30
37.59.52.42 attackbots
Attempt to hack Wordpress Login, XMLRPC or other login
2020-02-02 04:55:16
140.143.80.167 attackbots
...
2020-02-02 05:12:59
140.82.23.29 attackbots
Feb  1 21:38:46 [host] sshd[18212]: Invalid user uftp from 140.82.23.29
Feb  1 21:38:46 [host] sshd[18212]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.82.23.29
Feb  1 21:38:47 [host] sshd[18212]: Failed password for invalid user uftp from 140.82.23.29 port 60570 ssh2
2020-02-02 04:49:07
195.136.11.125 attackspam
Registration form abuse
2020-02-02 04:48:02
141.98.81.37 attack
Invalid user admin from 141.98.81.37 port 34605
2020-02-02 04:37:40
140.143.72.21 attackbots
Dec 13 04:43:07 v22018076590370373 sshd[18010]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.72.21 
...
2020-02-02 05:14:56
141.101.1.72 attackbotsspam
Feb 1 16:28:50 *host* sshd\[26277\]: Invalid user support from 141.101.1.72 port 53963 ...
2020-02-02 04:47:18
141.44.25.149 attackbots
Jan  7 06:51:15 v22018076590370373 sshd[7260]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.44.25.149 
...
2020-02-02 04:40:57
141.77.145.45 attackspam
...
2020-02-02 04:39:15
122.14.213.124 attackspambots
Unauthorized connection attempt detected from IP address 122.14.213.124 to port 2220 [J]
2020-02-02 05:15:30
139.198.255.55 attackbotsspam
Unauthorized connection attempt detected from IP address 139.198.255.55 to port 2220 [J]
2020-02-02 04:41:11

Recently Reported IPs

200.11.237.65 196.44.24.210 214.198.58.141 179.219.195.43
21.12.190.23 191.200.30.50 125.149.77.192 193.32.232.124
116.157.177.117 16.7.172.105 136.33.91.69 18.175.93.222
35.121.244.138 93.142.106.27 95.242.86.107 50.159.228.107
103.233.91.15 186.246.125.1 5.197.185.203 192.134.53.133