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: United States

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

;; QUESTION SECTION:
;104.22.14.225.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:25:26 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 225.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 225.14.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
123.21.143.75 attackspambots
xmlrpc attack
2020-08-04 04:36:47
114.67.241.174 attackbots
Aug  3 16:03:40 ws26vmsma01 sshd[17233]: Failed password for root from 114.67.241.174 port 62854 ssh2
...
2020-08-04 04:35:18
141.98.9.161 attackspambots
Aug  3 20:30:41 game-panel sshd[18240]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.9.161
Aug  3 20:30:42 game-panel sshd[18240]: Failed password for invalid user admin from 141.98.9.161 port 39201 ssh2
Aug  3 20:31:14 game-panel sshd[18287]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.9.161
2020-08-04 04:38:54
220.180.192.77 attackspambots
Aug  4 03:17:05 itv-usvr-01 sshd[20830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.180.192.77  user=root
Aug  4 03:17:07 itv-usvr-01 sshd[20830]: Failed password for root from 220.180.192.77 port 56828 ssh2
Aug  4 03:21:51 itv-usvr-01 sshd[21022]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.180.192.77  user=root
Aug  4 03:21:53 itv-usvr-01 sshd[21022]: Failed password for root from 220.180.192.77 port 41846 ssh2
Aug  4 03:26:05 itv-usvr-01 sshd[21245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.180.192.77  user=root
Aug  4 03:26:07 itv-usvr-01 sshd[21245]: Failed password for root from 220.180.192.77 port 51208 ssh2
2020-08-04 04:28:15
46.101.113.206 attackbots
Aug  3 20:16:48 ns382633 sshd\[26057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.113.206  user=root
Aug  3 20:16:50 ns382633 sshd\[26057\]: Failed password for root from 46.101.113.206 port 45610 ssh2
Aug  3 20:30:39 ns382633 sshd\[28552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.113.206  user=root
Aug  3 20:30:41 ns382633 sshd\[28552\]: Failed password for root from 46.101.113.206 port 39554 ssh2
Aug  3 20:34:23 ns382633 sshd\[28785\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.113.206  user=root
2020-08-04 04:11:46
23.82.29.250 attack
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - millnerchiro.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across millnerchiro.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over your si
2020-08-04 04:30:34
118.25.49.119 attackspambots
Aug  3 22:30:36 eventyay sshd[26692]: Failed password for root from 118.25.49.119 port 40502 ssh2
Aug  3 22:34:28 eventyay sshd[26878]: Failed password for root from 118.25.49.119 port 44720 ssh2
...
2020-08-04 04:40:51
185.17.141.208 attackspambots
Failed password for root from 185.17.141.208 port 38392 ssh2
2020-08-04 04:37:44
118.97.213.194 attackspambots
" "
2020-08-04 04:21:34
106.12.83.146 attack
Aug  3 17:50:17 mellenthin sshd[5139]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.83.146  user=root
Aug  3 17:50:19 mellenthin sshd[5139]: Failed password for invalid user root from 106.12.83.146 port 54676 ssh2
2020-08-04 04:33:30
104.227.121.24 attackbots
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - millnerchiro.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across millnerchiro.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over your si
2020-08-04 04:33:54
37.152.178.44 attackspambots
Aug  3 17:38:45 mail sshd[14547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.152.178.44  user=root
Aug  3 17:38:47 mail sshd[14547]: Failed password for root from 37.152.178.44 port 32804 ssh2
...
2020-08-04 04:14:13
217.182.23.55 attack
2020-08-03T20:17:30.863171abusebot-7.cloudsearch.cf sshd[28994]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip55.ip-217-182-23.eu  user=root
2020-08-03T20:17:33.355338abusebot-7.cloudsearch.cf sshd[28994]: Failed password for root from 217.182.23.55 port 48012 ssh2
2020-08-03T20:21:44.048764abusebot-7.cloudsearch.cf sshd[29093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip55.ip-217-182-23.eu  user=root
2020-08-03T20:21:45.653865abusebot-7.cloudsearch.cf sshd[29093]: Failed password for root from 217.182.23.55 port 47650 ssh2
2020-08-03T20:23:40.401959abusebot-7.cloudsearch.cf sshd[29155]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip55.ip-217-182-23.eu  user=root
2020-08-03T20:23:42.354723abusebot-7.cloudsearch.cf sshd[29155]: Failed password for root from 217.182.23.55 port 56006 ssh2
2020-08-03T20:25:31.728632abusebot-7.cloudsearch.cf sshd[29184]: pa
...
2020-08-04 04:33:14
119.145.101.190 attackbotsspam
Port scan: Attack repeated for 24 hours
2020-08-04 04:42:40
1.209.171.34 attack
Failed password for root from 1.209.171.34 port 40948 ssh2
2020-08-04 04:24:42

Recently Reported IPs

104.22.14.224 104.22.14.212 104.22.14.198 104.22.14.231
104.22.14.222 104.22.14.247 104.22.14.248 104.22.14.249
104.22.14.25 104.22.14.39 104.22.14.42 104.22.14.56
104.22.14.37 104.22.14.58 104.22.14.45 104.22.14.61
104.22.14.57 104.22.14.3 104.22.14.75 104.22.14.68