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

;; QUESTION SECTION:
;104.21.67.106.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 10:16:50 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 106.67.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 106.67.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
46.219.206.9 attackspam
Unauthorized connection attempt from IP address 46.219.206.9 on Port 445(SMB)
2019-12-01 23:47:51
110.137.101.23 attack
Unauthorized connection attempt from IP address 110.137.101.23 on Port 445(SMB)
2019-12-01 23:44:13
203.166.17.122 attackspambots
Unauthorized connection attempt from IP address 203.166.17.122 on Port 445(SMB)
2019-12-01 23:26:24
118.24.101.182 attackbots
Dec  1 16:52:33 mout sshd[22120]: Invalid user Aa123456789 from 118.24.101.182 port 54376
2019-12-02 00:03:32
218.92.0.137 attack
Dec  1 16:57:25 localhost sshd\[23288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.137  user=root
Dec  1 16:57:27 localhost sshd\[23288\]: Failed password for root from 218.92.0.137 port 46767 ssh2
Dec  1 16:57:31 localhost sshd\[23288\]: Failed password for root from 218.92.0.137 port 46767 ssh2
2019-12-01 23:58:39
106.12.98.7 attack
Dec  1 17:41:25 server sshd\[26323\]: Invalid user soonman from 106.12.98.7 port 49334
Dec  1 17:41:25 server sshd\[26323\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.98.7
Dec  1 17:41:27 server sshd\[26323\]: Failed password for invalid user soonman from 106.12.98.7 port 49334 ssh2
Dec  1 17:45:24 server sshd\[30901\]: Invalid user myroot from 106.12.98.7 port 51898
Dec  1 17:45:24 server sshd\[30901\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.98.7
2019-12-01 23:56:08
213.55.92.56 attackspam
Unauthorized connection attempt from IP address 213.55.92.56 on Port 445(SMB)
2019-12-01 23:27:45
46.38.144.17 attack
Dec  1 16:57:25 relay postfix/smtpd\[18446\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  1 16:57:52 relay postfix/smtpd\[4808\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  1 16:58:02 relay postfix/smtpd\[18446\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  1 16:58:30 relay postfix/smtpd\[6935\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  1 16:58:39 relay postfix/smtpd\[16256\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-02 00:01:20
52.69.203.57 attack
Message ID	
Created at:	Sun, Dec 1, 2019 at 8:37 AM (Delivered after -2114 seconds)
From:	⚠️ Unsubscribe ⚠️ 
Subject:	❤️Welcome to 'Christmas Adult sex' ❤️
SPF:	PASS with IP 52.69.203.57
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: best guess record for domain of eulmaomz@donyo---donyo----us-west-2.compute.amazonaws.com designates 52.69.203.57 as permitted sender) smtp.mailfrom=EUlmAOMz@donyo---donyo----us-west-2.compute.amazonaws.com
Return-Path: 
Received: from cyborganic.com (ec2-52-69-203-57.ap-northeast-1.compute.amazonaws.com. [52.69.203.57])
        by mx.google.com with ESMTP id j11si27086713pgj.218.2019.12.01.06.01.50
2019-12-01 23:35:24
134.175.111.215 attackspam
Dec  1 15:57:16 lnxded63 sshd[31018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.111.215
2019-12-01 23:32:56
58.69.139.152 attackspambots
firewall-block, port(s): 26/tcp
2019-12-01 23:58:04
111.230.241.245 attack
Dec 01 08:39:46 askasleikir sshd[102830]: Failed password for invalid user user3 from 111.230.241.245 port 35182 ssh2
2019-12-01 23:55:42
129.213.122.26 attackspam
Dec  1 16:50:29 legacy sshd[586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26
Dec  1 16:50:30 legacy sshd[586]: Failed password for invalid user sanne from 129.213.122.26 port 44030 ssh2
Dec  1 16:53:43 legacy sshd[807]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26
...
2019-12-02 00:02:43
183.203.96.56 attack
Fail2Ban - SSH Bruteforce Attempt
2019-12-01 23:22:52
154.16.53.24 attack
(From eric@talkwithcustomer.com) Hey,

You have a website mikulachiropractic.net, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a
2019-12-01 23:28:12

Recently Reported IPs

104.21.66.88 104.21.66.71 104.21.67.13 104.21.67.140
104.21.67.130 104.21.67.12 104.21.67.169 104.21.67.150
104.21.67.119 104.21.67.168 104.21.67.172 104.21.67.122
104.21.67.143 104.21.67.176 13.225.71.61 104.21.67.189
104.21.67.225 104.21.67.25 104.21.67.249 104.21.67.213