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

;; QUESTION SECTION:
;104.21.70.129.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:48:33 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 129.70.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 129.70.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
200.73.128.181 attack
Jun 27 05:44:19 game-panel sshd[21631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.73.128.181
Jun 27 05:44:21 game-panel sshd[21631]: Failed password for invalid user saurabh from 200.73.128.181 port 50292 ssh2
Jun 27 05:48:41 game-panel sshd[21818]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.73.128.181
2020-06-27 18:50:36
36.111.182.128 attackbotsspam
firewall-block, port(s): 13573/tcp
2020-06-27 19:28:31
46.32.45.207 attackbotsspam
Jun 27 03:44:38 mockhub sshd[12593]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.32.45.207
Jun 27 03:44:40 mockhub sshd[12593]: Failed password for invalid user lex from 46.32.45.207 port 38262 ssh2
...
2020-06-27 18:54:57
62.234.135.100 attack
Jun 27 16:39:41 localhost sshd[1331995]: Connection closed by 62.234.135.100 port 48408 [preauth]
...
2020-06-27 19:26:21
64.111.121.238 attackspam
Automatic report - XMLRPC Attack
2020-06-27 18:46:02
183.83.66.230 attackspambots
Unauthorised access (Jun 27) SRC=183.83.66.230 LEN=52 TTL=113 ID=11294 DF TCP DPT=445 WINDOW=8192 SYN
2020-06-27 18:51:01
107.172.229.157 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found loischiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software th
2020-06-27 19:22:09
175.138.108.78 attackspambots
2020-06-27T09:57:20.534871dmca.cloudsearch.cf sshd[12963]: Invalid user indrajit from 175.138.108.78 port 55288
2020-06-27T09:57:20.540274dmca.cloudsearch.cf sshd[12963]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.138.108.78
2020-06-27T09:57:20.534871dmca.cloudsearch.cf sshd[12963]: Invalid user indrajit from 175.138.108.78 port 55288
2020-06-27T09:57:22.696538dmca.cloudsearch.cf sshd[12963]: Failed password for invalid user indrajit from 175.138.108.78 port 55288 ssh2
2020-06-27T10:00:56.561635dmca.cloudsearch.cf sshd[13089]: Invalid user solange from 175.138.108.78 port 54529
2020-06-27T10:00:56.567552dmca.cloudsearch.cf sshd[13089]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.138.108.78
2020-06-27T10:00:56.561635dmca.cloudsearch.cf sshd[13089]: Invalid user solange from 175.138.108.78 port 54529
2020-06-27T10:00:58.711857dmca.cloudsearch.cf sshd[13089]: Failed password for invalid user s
...
2020-06-27 19:09:46
128.199.110.226 attackbots
TCP port : 13235
2020-06-27 19:17:50
212.70.149.50 attack
(smtpauth) Failed SMTP AUTH login from 212.70.149.50 (BG/Bulgaria/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-06-27 15:47:33 login authenticator failed for (User) [212.70.149.50]: 535 Incorrect authentication data (set_id=records@farasunict.com)
2020-06-27 19:27:08
36.22.187.34 attackspam
2020-06-26T23:33:00.624203hostname sshd[27214]: Invalid user lqy from 36.22.187.34 port 46076
2020-06-26T23:33:02.784823hostname sshd[27214]: Failed password for invalid user lqy from 36.22.187.34 port 46076 ssh2
2020-06-26T23:37:07.448447hostname sshd[30307]: Invalid user postgres from 36.22.187.34 port 55870
...
2020-06-27 19:19:48
118.36.234.187 attackspam
Jun 27 11:12:13 web8 sshd\[6013\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.36.234.187  user=root
Jun 27 11:12:16 web8 sshd\[6013\]: Failed password for root from 118.36.234.187 port 51890 ssh2
Jun 27 11:16:03 web8 sshd\[8119\]: Invalid user ftb from 118.36.234.187
Jun 27 11:16:03 web8 sshd\[8119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.36.234.187
Jun 27 11:16:06 web8 sshd\[8119\]: Failed password for invalid user ftb from 118.36.234.187 port 53580 ssh2
2020-06-27 19:16:15
124.240.197.238 attackbotsspam
Hits on port : 445
2020-06-27 19:00:27
52.163.203.13 attack
sshd: Failed password for .... from 52.163.203.13 port 2819 ssh2 (3 attempts)
2020-06-27 18:56:19
178.62.192.156 attackbotsspam
Invalid user admin from 178.62.192.156 port 43898
2020-06-27 19:12:36

Recently Reported IPs

104.21.70.128 104.21.70.135 104.21.70.133 104.21.71.150
104.21.70.13 104.21.70.137 104.21.70.141 104.21.70.139
104.21.70.146 104.21.70.15 104.21.70.156 104.21.71.151
104.21.70.151 104.21.70.153 104.21.70.154 104.21.70.163
104.21.70.169 104.21.70.16 104.21.70.168 104.21.70.171