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

;; QUESTION SECTION:
;104.22.14.63.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:09:48 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 63.14.22.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 63.14.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.203.201.89 attackbots
*Port Scan* detected from 159.203.201.89 (US/United States/zg-0911a-132.stretchoid.com). 4 hits in the last 166 seconds
2020-01-24 13:07:27
51.77.144.50 attack
Jan 24 05:58:17 [host] sshd[32192]: Invalid user prueba from 51.77.144.50
Jan 24 05:58:17 [host] sshd[32192]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.144.50
Jan 24 05:58:19 [host] sshd[32192]: Failed password for invalid user prueba from 51.77.144.50 port 32858 ssh2
2020-01-24 13:10:55
36.91.165.39 attackspam
Unauthorized connection attempt from IP address 36.91.165.39 on Port 445(SMB)
2020-01-24 09:48:06
104.140.83.156 attack
(From eric@talkwithcustomer.com) 
Hi,

Let’s take a quick trip to Tomorrow-land.

I’m not talking about a theme park, I’m talking about your business’s future…

Don’t worry, we won’t even need a crystal ball.  

Just imagine… 

… a future where the money you invest in driving traffic to your site denvertechchiro.com pays off with tons of calls from qualified leads.
 
And the difference between what you experienced in the past is staggering – you’re seeing 10X, 20X, 50X, even up to a 100X more leads coming from your website denvertechchiro.com.  Leads that are already engaged with what you have to offer and are ready to learn more and even open their wallets.

Seeing all this taking place in your business, you think back: What did I do only a short time ago that made such a huge difference?

And then it hits you: You took advantage of a free 14 day Test Drive of TalkWithCustomer.

You installed TalkWithCustomer on denvertechchiro.com – it was a snap.

And practically overnight customers st
2020-01-24 13:01:31
220.181.108.173 attackspambots
Bad bot/spoofed identity
2020-01-24 13:21:07
139.195.245.113 attack
Unauthorized connection attempt from IP address 139.195.245.113 on Port 139(NETBIOS)
2020-01-24 09:56:05
77.241.193.14 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/77.241.193.14/ 
 
 LT - 1H : (1)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : LT 
 NAME ASN : ASN15440 
 
 IP : 77.241.193.14 
 
 CIDR : 77.241.192.0/20 
 
 PREFIX COUNT : 36 
 
 UNIQUE IP COUNT : 34304 
 
 
 ATTACKS DETECTED ASN15440 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2020-01-24 05:54:59 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2020-01-24 13:13:00
218.248.18.211 attackbots
Unauthorized connection attempt from IP address 218.248.18.211 on Port 445(SMB)
2020-01-24 09:46:11
222.186.173.226 attackbotsspam
2020-01-24T02:37:09.497916vps751288.ovh.net sshd\[5782\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.226  user=root
2020-01-24T02:37:11.979380vps751288.ovh.net sshd\[5782\]: Failed password for root from 222.186.173.226 port 1413 ssh2
2020-01-24T02:37:15.247969vps751288.ovh.net sshd\[5782\]: Failed password for root from 222.186.173.226 port 1413 ssh2
2020-01-24T02:37:18.261603vps751288.ovh.net sshd\[5782\]: Failed password for root from 222.186.173.226 port 1413 ssh2
2020-01-24T02:37:21.686370vps751288.ovh.net sshd\[5782\]: Failed password for root from 222.186.173.226 port 1413 ssh2
2020-01-24 09:47:00
82.64.40.245 attack
(sshd) Failed SSH login from 82.64.40.245 (FR/France/82-64-40-245.subs.proxad.net): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jan 24 05:54:49 ubnt-55d23 sshd[19522]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.64.40.245  user=root
Jan 24 05:54:52 ubnt-55d23 sshd[19522]: Failed password for root from 82.64.40.245 port 57666 ssh2
2020-01-24 13:16:54
78.95.124.228 attackbots
TCP Port: 25      invalid blocked  dnsbl-sorbs also abuseat-org and barracuda           (16)
2020-01-24 09:37:57
103.111.110.154 attack
Jan 24 05:55:01 herz-der-gamer sshd[10555]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.111.110.154  user=root
Jan 24 05:55:04 herz-der-gamer sshd[10555]: Failed password for root from 103.111.110.154 port 39776 ssh2
...
2020-01-24 13:07:48
179.225.218.68 attack
Unauthorized connection attempt from IP address 179.225.218.68 on Port 445(SMB)
2020-01-24 09:44:09
112.64.34.165 attack
Jan 24 03:44:21 pkdns2 sshd\[10729\]: Invalid user fg from 112.64.34.165Jan 24 03:44:24 pkdns2 sshd\[10729\]: Failed password for invalid user fg from 112.64.34.165 port 58807 ssh2Jan 24 03:47:36 pkdns2 sshd\[10954\]: Invalid user account from 112.64.34.165Jan 24 03:47:38 pkdns2 sshd\[10954\]: Failed password for invalid user account from 112.64.34.165 port 42022 ssh2Jan 24 03:50:51 pkdns2 sshd\[11196\]: Invalid user cos from 112.64.34.165Jan 24 03:50:53 pkdns2 sshd\[11196\]: Failed password for invalid user cos from 112.64.34.165 port 53471 ssh2
...
2020-01-24 09:53:07
92.63.194.26 attackbots
SSH bruteforce (Triggered fail2ban)
2020-01-24 13:23:06

Recently Reported IPs

36.110.96.184 104.22.14.66 104.22.14.73 134.39.93.101
134.36.2.74 134.122.130.207 134.39.250.10 134.29.163.151
134.255.202.8 134.35.198.216 134.39.180.76 134.29.239.116
104.22.14.81 134.29.217.1 134.39.44.146 134.29.152.158
134.58.65.0 134.54.224.30 134.58.134.15 134.6.94.87