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: Medellín

Region: Antioquia

Country: Colombia

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

;; QUESTION SECTION:
;190.249.50.139.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 31 17:41:41 CST 2023
;; MSG SIZE  rcvd: 107
Host info
139.50.249.190.in-addr.arpa domain name pointer cable190-249-50-139.epm.net.co.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.50.249.190.in-addr.arpa	name = cable190-249-50-139.epm.net.co.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.119.174.102 attack
Malicious/Probing: /wp-includes/wlwmanifest.xml
2020-04-24 17:59:08
183.63.87.236 attackbotsspam
Invalid user ftpuser from 183.63.87.236 port 50796
2020-04-24 18:01:57
83.30.98.27 attackbots
Brute force attempt
2020-04-24 17:47:02
89.248.174.216 attack
Apr 24 11:21:01 debian-2gb-nbg1-2 kernel: \[9979006.428514\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.174.216 DST=195.201.40.59 LEN=488 TOS=0x00 PREC=0x00 TTL=247 ID=54321 PROTO=UDP SPT=46221 DPT=53413 LEN=468
2020-04-24 17:49:59
60.19.64.10 attackspambots
2020-04-24T04:48:30.238571beta postfix/smtpd[27416]: warning: unknown[60.19.64.10]: SASL LOGIN authentication failed: authentication failure
2020-04-24T04:48:36.156670beta postfix/smtpd[27416]: warning: unknown[60.19.64.10]: SASL LOGIN authentication failed: authentication failure
2020-04-24T04:48:48.998700beta postfix/smtpd[27416]: warning: unknown[60.19.64.10]: SASL LOGIN authentication failed: authentication failure
...
2020-04-24 18:14:47
77.40.70.254 attackspam
Brute force attempt
2020-04-24 18:14:35
106.13.175.126 attack
prod8
...
2020-04-24 18:19:16
79.124.62.86 attackbotsspam
ET CINS Active Threat Intelligence Poor Reputation IP group 65 - port: 2278 proto: TCP cat: Misc Attack
2020-04-24 17:57:25
67.205.167.193 attack
Apr 24 09:47:17 ip-172-31-61-156 sshd[20297]: Invalid user testuser from 67.205.167.193
Apr 24 09:47:17 ip-172-31-61-156 sshd[20297]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.167.193
Apr 24 09:47:17 ip-172-31-61-156 sshd[20297]: Invalid user testuser from 67.205.167.193
Apr 24 09:47:19 ip-172-31-61-156 sshd[20297]: Failed password for invalid user testuser from 67.205.167.193 port 39518 ssh2
Apr 24 09:50:14 ip-172-31-61-156 sshd[20944]: Invalid user admin from 67.205.167.193
...
2020-04-24 18:06:50
1.209.171.34 attackbots
Bruteforce detected by fail2ban
2020-04-24 18:23:54
35.195.238.142 attackbotsspam
SSH authentication failure x 6 reported by Fail2Ban
...
2020-04-24 18:15:48
37.49.226.180 attackbotsspam
[Block] Port Scanning | Rate: 10 hits/1hr
2020-04-24 18:21:15
183.185.187.197 attack
FTP/21 MH Probe, BF, Hack -
2020-04-24 18:16:10
163.172.188.175 spambots
Spam
2020-04-24 18:23:50
163.53.204.182 attackbotsspam
bruteforce detected
2020-04-24 18:23:08

Recently Reported IPs

211.66.61.10 3.110.218.103 118.66.165.116 133.245.179.168
41.135.48.202 231.60.30.141 178.128.220.107 103.108.34.64
46.114.155.30 46.231.5.113 103.90.156.66 182.225.24.147
119.2.60.17 174.8.78.99 174.36.209.215 174.36.48.138
38.161.140.131 117.53.78.62 118.255.173.39 138.201.189.142