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

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

;; QUESTION SECTION:
;104.139.67.49.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 19:18:52 CST 2022
;; MSG SIZE  rcvd: 106
Host info
49.67.139.104.in-addr.arpa domain name pointer cpe-104-139-67-49.carolina.res.rr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
49.67.139.104.in-addr.arpa	name = cpe-104-139-67-49.carolina.res.rr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
72.221.232.136 attackbotsspam
(imapd) Failed IMAP login from 72.221.232.136 (US/United States/-): 1 in the last 3600 secs
2019-12-31 13:57:47
223.71.167.164 attackspambots
scan z
2019-12-31 14:21:41
122.51.115.226 attackspambots
Invalid user oseas from 122.51.115.226 port 57274
2019-12-31 14:17:38
182.74.68.58 attack
Unauthorized connection attempt detected from IP address 182.74.68.58 to port 445
2019-12-31 14:01:30
171.228.0.191 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 31-12-2019 04:55:09.
2019-12-31 14:19:16
222.186.175.183 attack
2019-12-31T06:13:30.135738abusebot-5.cloudsearch.cf sshd[30600]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.183  user=root
2019-12-31T06:13:31.730533abusebot-5.cloudsearch.cf sshd[30600]: Failed password for root from 222.186.175.183 port 41324 ssh2
2019-12-31T06:13:34.840159abusebot-5.cloudsearch.cf sshd[30600]: Failed password for root from 222.186.175.183 port 41324 ssh2
2019-12-31T06:13:30.135738abusebot-5.cloudsearch.cf sshd[30600]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.183  user=root
2019-12-31T06:13:31.730533abusebot-5.cloudsearch.cf sshd[30600]: Failed password for root from 222.186.175.183 port 41324 ssh2
2019-12-31T06:13:34.840159abusebot-5.cloudsearch.cf sshd[30600]: Failed password for root from 222.186.175.183 port 41324 ssh2
2019-12-31T06:13:30.135738abusebot-5.cloudsearch.cf sshd[30600]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 
...
2019-12-31 14:22:57
46.38.144.179 attackspambots
Dec 31 06:54:46 relay postfix/smtpd\[26484\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 06:57:14 relay postfix/smtpd\[26874\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 06:58:00 relay postfix/smtpd\[25529\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 07:00:26 relay postfix/smtpd\[12333\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 07:01:21 relay postfix/smtpd\[25529\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-31 14:11:37
106.12.99.173 attackspam
Dec 31 05:55:38 MK-Soft-VM5 sshd[30796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.99.173 
Dec 31 05:55:40 MK-Soft-VM5 sshd[30796]: Failed password for invalid user mysql from 106.12.99.173 port 43362 ssh2
...
2019-12-31 13:57:27
69.80.70.115 attack
firewall-block, port(s): 1433/tcp
2019-12-31 14:24:57
45.114.179.215 attackbots
1577768123 - 12/31/2019 05:55:23 Host: 45.114.179.215/45.114.179.215 Port: 445 TCP Blocked
2019-12-31 14:12:00
49.235.16.103 attack
Dec 31 05:36:32 saengerschafter sshd[22291]: Invalid user zarah from 49.235.16.103
Dec 31 05:36:32 saengerschafter sshd[22291]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.16.103 
Dec 31 05:36:34 saengerschafter sshd[22291]: Failed password for invalid user zarah from 49.235.16.103 port 38330 ssh2
Dec 31 05:36:34 saengerschafter sshd[22291]: Received disconnect from 49.235.16.103: 11: Bye Bye [preauth]
Dec 31 06:02:13 saengerschafter sshd[24578]: Invalid user muru from 49.235.16.103
Dec 31 06:02:13 saengerschafter sshd[24578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.16.103 
Dec 31 06:02:16 saengerschafter sshd[24578]: Failed password for invalid user muru from 49.235.16.103 port 51618 ssh2
Dec 31 06:02:16 saengerschafter sshd[24578]: Received disconnect from 49.235.16.103: 11: Bye Bye [preauth]
Dec 31 06:08:17 saengerschafter sshd[25022]: Invalid user guest from 49.........
-------------------------------
2019-12-31 13:57:12
222.186.175.212 attackspam
19/12/31@01:13:35: FAIL: IoT-SSH address from=222.186.175.212
...
2019-12-31 14:14:26
46.233.10.106 attack
invalid login attempt (rwilliams)
2019-12-31 14:09:51
82.178.234.69 attack
12/31/2019-05:55:25.724621 82.178.234.69 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-31 14:10:19
63.83.78.89 attackspam
$f2bV_matches
2019-12-31 14:23:19

Recently Reported IPs

104.139.66.54 104.139.66.49 104.139.66.98 101.109.151.114
104.139.66.200 104.139.68.184 104.139.68.13 101.109.151.124
104.139.69.103 104.139.68.8 104.139.68.201 104.139.68.196
104.139.68.60 101.109.151.13 101.109.151.132 101.109.151.136
104.140.73.66 104.143.44.135 104.143.32.17 104.143.41.74