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

;; QUESTION SECTION:
;104.139.24.13.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 16:07:51 CST 2022
;; MSG SIZE  rcvd: 106
Host info
13.24.139.104.in-addr.arpa domain name pointer cpe-104-139-24-13.carolina.res.rr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
13.24.139.104.in-addr.arpa	name = cpe-104-139-24-13.carolina.res.rr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.232.153.169 attack
Detected by Maltrail
2020-07-02 05:15:05
192.227.139.241 attackspambots
(From cynthia.frederic@hotmail.com) Hi,

Do you have a Website? Of course you do because I am looking at your website nikitowchiropractic.com now.

Are you struggling for Leads and Sales?

You’re not the only one.

So many Website owners struggle to convert their Visitors into Leads & Sales.

There’s a simple way to fix this problem.

You could use a Live Chat app on your Website nikitowchiropractic.com and hire Chat Agents.

But only if you’ve got deep pockets and you’re happy to fork out THOUSANDS of dollars for the quality you need.

=====

But what if you could automate Live Chat so it’s HUMAN-FREE?

What if you could exploit NEW “AI” Technology to engage with your Visitors INSTANTLY.

And AUTOMATICALLY convert them into Leads & Sales.

WITHOUT spending THOUSANDS of dollars on Live Chat Agents.

And WITHOUT hiring expensive coders.

In fact, all you need to do to activate this LATEST “AI” Website Tech..

..is to COPY & PASTE a single line of “Website Code”.

==> http://www.
2020-07-02 05:06:27
171.244.140.174 attackspam
775. On Jun 30 2020 experienced a Brute Force SSH login attempt -> 2 unique times by 171.244.140.174.
2020-07-02 05:29:59
103.81.86.49 attackbotsspam
Failed password for invalid user zmy from 103.81.86.49 port 58365 ssh2
2020-07-02 05:47:59
222.186.15.18 attack
Jun 30 19:55:54 ny01 sshd[32617]: Failed password for root from 222.186.15.18 port 35553 ssh2
Jun 30 19:59:06 ny01 sshd[693]: Failed password for root from 222.186.15.18 port 15362 ssh2
2020-07-02 05:25:34
43.249.140.98 attackbots
(sshd) Failed SSH login from 43.249.140.98 (ID/Indonesia/ych.skyline.net.id): 5 in the last 3600 secs
2020-07-02 05:20:20
87.121.76.189 attackbotsspam
Jul  1 02:48:11 www2 sshd\[25414\]: Invalid user ubnt from 87.121.76.189Jul  1 02:48:13 www2 sshd\[25414\]: Failed password for invalid user ubnt from 87.121.76.189 port 54131 ssh2Jul  1 02:48:16 www2 sshd\[25414\]: Failed password for invalid user ubnt from 87.121.76.189 port 54131 ssh2
...
2020-07-02 05:28:36
137.74.166.77 attack
Jul  1 00:26:13 pve1 sshd[21021]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.166.77 
Jul  1 00:26:15 pve1 sshd[21021]: Failed password for invalid user mysql from 137.74.166.77 port 37432 ssh2
...
2020-07-02 05:46:19
185.234.216.38 attack
Hacking
2020-07-02 05:45:05
87.121.77.137 attack
Jul  1 01:29:18 mail sshd\[26459\]: Invalid user ubnt from 87.121.77.137
Jul  1 01:29:18 mail sshd\[26459\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.121.77.137
Jul  1 01:29:20 mail sshd\[26459\]: Failed password for invalid user ubnt from 87.121.77.137 port 60483 ssh2
2020-07-02 05:14:22
31.41.255.34 attack
SSH Brute-Force reported by Fail2Ban
2020-07-02 06:04:50
220.173.140.245 attackbots
 TCP (SYN) 220.173.140.245:62104 -> port 1433, len 52
2020-07-02 05:17:36
107.182.177.38 attack
Jun 30 16:47:37 mockhub sshd[7000]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.182.177.38
Jun 30 16:47:39 mockhub sshd[7000]: Failed password for invalid user javier from 107.182.177.38 port 54752 ssh2
...
2020-07-02 05:07:12
64.227.26.221 attack
Port scan denied
2020-07-02 05:58:37
51.254.222.108 attackbotsspam
Jul  1 00:06:28 web-main sshd[116575]: Invalid user lizk from 51.254.222.108 port 51220
Jul  1 00:06:30 web-main sshd[116575]: Failed password for invalid user lizk from 51.254.222.108 port 51220 ssh2
Jul  1 00:21:53 web-main sshd[116649]: Invalid user postgres from 51.254.222.108 port 60656
2020-07-02 05:59:21

Recently Reported IPs

131.14.141.168 176.106.197.128 156.41.27.94 230.97.15.148
134.33.26.38 165.179.34.112 166.244.197.251 145.56.84.72
159.174.189.14 243.95.118.148 208.141.159.57 252.66.51.125
142.209.132.133 239.77.153.57 233.96.127.224 185.16.200.171
253.56.129.18 111.121.207.26 134.135.144.163 115.141.224.201