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

;; QUESTION SECTION:
;104.21.34.77.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 21:01:52 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 77.34.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 77.34.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.32.120.141 attackspambots
Dec 29 07:23:34 grey postfix/smtpd\[1445\]: NOQUEUE: reject: RCPT from ip141.ip-178-32-120.eu\[178.32.120.141\]: 554 5.7.1 Service unavailable\; Client host \[178.32.120.141\] blocked using bl.spamcop.net\; Blocked - see https://www.spamcop.net/bl.shtml\?178.32.120.141\; from=\ to=\ proto=ESMTP helo=\
...
2019-12-29 22:51:54
217.16.11.235 attackbots
12/29/2019-01:23:51.379778 217.16.11.235 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-12-29 22:40:47
188.247.65.179 attackbots
Dec 29 07:43:50 server sshd\[873\]: Invalid user yokoi from 188.247.65.179
Dec 29 07:43:50 server sshd\[873\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.247.65.179 
Dec 29 07:43:52 server sshd\[873\]: Failed password for invalid user yokoi from 188.247.65.179 port 39636 ssh2
Dec 29 17:55:11 server sshd\[32002\]: Invalid user dl from 188.247.65.179
Dec 29 17:55:11 server sshd\[32002\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.247.65.179 
...
2019-12-29 23:00:33
52.52.190.187 attackspambots
Malicious/Probing: /wp-login.php
2019-12-29 22:46:52
83.4.232.223 attackbots
Automatic report - Port Scan Attack
2019-12-29 22:53:32
198.199.122.234 attackspam
Dec 29 04:25:47 vps46666688 sshd[31824]: Failed password for root from 198.199.122.234 port 38266 ssh2
...
2019-12-29 22:49:55
144.76.38.40 attackbotsspam
20 attempts against mh-misbehave-ban on pluto.magehost.pro
2019-12-29 22:46:28
175.5.33.174 attackbots
Scanning
2019-12-29 22:54:08
118.126.111.108 attackbotsspam
Dec 29 15:54:20 herz-der-gamer sshd[14317]: Invalid user guest from 118.126.111.108 port 39988
Dec 29 15:54:20 herz-der-gamer sshd[14317]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.126.111.108
Dec 29 15:54:20 herz-der-gamer sshd[14317]: Invalid user guest from 118.126.111.108 port 39988
Dec 29 15:54:22 herz-der-gamer sshd[14317]: Failed password for invalid user guest from 118.126.111.108 port 39988 ssh2
...
2019-12-29 23:17:52
107.173.209.21 attackbotsspam
(From eric@talkwithcustomer.com)  
Hey,

You have a website livewithvitality.com, 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-29 22:44:33
115.120.0.0 attackbots
Dec 29 12:56:50 server sshd\[29888\]: Invalid user temp from 115.120.0.0
Dec 29 12:56:50 server sshd\[29888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.120.0.0 
Dec 29 12:56:52 server sshd\[29888\]: Failed password for invalid user temp from 115.120.0.0 port 25939 ssh2
Dec 29 13:08:53 server sshd\[32433\]: Invalid user blascow from 115.120.0.0
Dec 29 13:08:53 server sshd\[32433\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.120.0.0 
...
2019-12-29 22:56:32
222.186.180.147 attack
Dec 29 10:20:39 TORMINT sshd\[3126\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147  user=root
Dec 29 10:20:41 TORMINT sshd\[3126\]: Failed password for root from 222.186.180.147 port 5012 ssh2
Dec 29 10:21:00 TORMINT sshd\[3133\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147  user=root
...
2019-12-29 23:26:02
72.52.156.83 attackspambots
Automatic report - XMLRPC Attack
2019-12-29 23:11:05
165.227.97.188 attackbots
Dec 29 15:55:04 icinga sshd[11835]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.97.188
Dec 29 15:55:06 icinga sshd[11835]: Failed password for invalid user shawaii from 165.227.97.188 port 35504 ssh2
...
2019-12-29 23:04:33
84.123.29.147 attack
Dec 29 15:54:58 MK-Soft-VM5 sshd[21511]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.123.29.147 
Dec 29 15:55:00 MK-Soft-VM5 sshd[21511]: Failed password for invalid user admin from 84.123.29.147 port 41047 ssh2
...
2019-12-29 23:10:16

Recently Reported IPs

104.21.34.76 104.21.34.78 104.21.34.8 104.21.34.82
104.21.34.84 104.21.34.88 104.21.34.90 104.21.34.91
104.21.34.97 104.21.35.10 104.21.35.101 104.21.35.104
104.21.35.107 104.21.35.110 104.21.35.118 104.21.35.119
104.21.35.120 165.64.99.207 104.21.35.122 161.202.248.42