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

;; QUESTION SECTION:
;104.21.22.149.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 19:01:22 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 149.22.21.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 149.22.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.119.160.143 attackbots
12/21/2019-16:29:23.885577 92.119.160.143 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-12-22 06:54:41
164.132.209.242 attack
Invalid user wrobel from 164.132.209.242 port 59572
2019-12-22 07:25:37
35.236.69.199 attackspam
Invalid user test from 35.236.69.199 port 44684
2019-12-22 07:22:23
192.3.143.47 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 bissland.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 bissland.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 bissland.com – it was a snap.

And practically overnight customers started engaging more r
2019-12-22 07:19:25
138.197.152.113 attackbotsspam
Invalid user cvsroot from 138.197.152.113 port 59552
2019-12-22 07:08:01
181.48.65.122 attack
2019-12-21 23:56:56 H=([181.48.65.122]) [181.48.65.122] F= rejected RCPT : relay not permitted
2019-12-21 23:58:35 H=([181.48.65.122]) [181.48.65.122] F= rejected RCPT : relay not permitted
...
2019-12-22 07:03:28
107.175.37.113 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 bissland.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 bissland.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 bissland.com – it was a snap.

And practically overnight customers started engaging more r
2019-12-22 07:14:03
62.234.128.242 attackbots
Dec 22 01:41:12 server sshd\[30212\]: Invalid user admin from 62.234.128.242
Dec 22 01:41:12 server sshd\[30212\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.128.242 
Dec 22 01:41:15 server sshd\[30212\]: Failed password for invalid user admin from 62.234.128.242 port 47800 ssh2
Dec 22 02:05:39 server sshd\[4619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.128.242  user=root
Dec 22 02:05:40 server sshd\[4619\]: Failed password for root from 62.234.128.242 port 59744 ssh2
...
2019-12-22 07:10:42
221.122.67.66 attackbots
Dec 21 23:11:56 hcbbdb sshd\[5821\]: Invalid user admin from 221.122.67.66
Dec 21 23:11:56 hcbbdb sshd\[5821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.67.66
Dec 21 23:11:58 hcbbdb sshd\[5821\]: Failed password for invalid user admin from 221.122.67.66 port 33535 ssh2
Dec 21 23:16:39 hcbbdb sshd\[6320\]: Invalid user franek from 221.122.67.66
Dec 21 23:16:39 hcbbdb sshd\[6320\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.67.66
2019-12-22 07:29:38
36.26.78.36 attack
Dec 22 02:50:40 microserver sshd[18635]: Invalid user vagrant from 36.26.78.36 port 55202
Dec 22 02:50:40 microserver sshd[18635]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.26.78.36
Dec 22 02:50:42 microserver sshd[18635]: Failed password for invalid user vagrant from 36.26.78.36 port 55202 ssh2
Dec 22 02:58:26 microserver sshd[19671]: Invalid user demo from 36.26.78.36 port 51810
Dec 22 02:58:26 microserver sshd[19671]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.26.78.36
2019-12-22 07:15:57
103.196.29.22 attack
failed_logins
2019-12-22 07:02:35
5.9.100.40 attack
20 attempts against mh-misbehave-ban on flare.magehost.pro
2019-12-22 06:55:48
49.232.51.61 attackbots
Dec 22 01:47:33 server sshd\[31791\]: Invalid user nianekeo from 49.232.51.61
Dec 22 01:47:33 server sshd\[31791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.51.61 
Dec 22 01:47:36 server sshd\[31791\]: Failed password for invalid user nianekeo from 49.232.51.61 port 56170 ssh2
Dec 22 02:07:25 server sshd\[4957\]: Invalid user song from 49.232.51.61
Dec 22 02:07:25 server sshd\[4957\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.51.61 
...
2019-12-22 07:11:52
54.38.242.233 attackspambots
Invalid user carlos from 54.38.242.233 port 52100
2019-12-22 07:27:24
83.61.10.169 attack
detected by Fail2Ban
2019-12-22 06:56:18

Recently Reported IPs

222.0.22.88 104.21.22.150 104.21.22.151 104.21.22.157
104.21.22.158 104.21.22.160 104.21.22.161 104.21.22.164
216.191.77.25 104.21.22.165 104.21.22.167 104.21.22.173
104.21.22.18 6.28.22.152 104.21.22.181 104.21.22.185
104.21.22.186 104.21.22.188 104.21.22.190 104.21.22.192