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

;; QUESTION SECTION:
;104.21.53.111.			IN	A

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

;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 23:54:58 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 111.53.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 111.53.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.70.100.23 attackbotsspam
CMS (WordPress or Joomla) login attempt.
2020-04-18 18:29:21
80.211.128.151 attackspambots
firewall-block, port(s): 20231/tcp
2020-04-18 18:39:51
218.92.0.175 attackspam
$f2bV_matches
2020-04-18 19:00:33
212.64.17.247 attackspambots
Apr 18 11:02:14 server sshd[31780]: Failed password for invalid user gi from 212.64.17.247 port 34650 ssh2
Apr 18 11:10:10 server sshd[5204]: Failed password for invalid user fw from 212.64.17.247 port 55580 ssh2
Apr 18 11:12:45 server sshd[7127]: Failed password for root from 212.64.17.247 port 50906 ssh2
2020-04-18 18:21:38
209.58.157.196 attack
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across medenchiropractic.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
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 signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www
2020-04-18 18:47:25
13.233.112.7 attackbots
Apr 18 12:02:07 santamaria sshd\[23587\]: Invalid user ul from 13.233.112.7
Apr 18 12:02:07 santamaria sshd\[23587\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.233.112.7
Apr 18 12:02:09 santamaria sshd\[23587\]: Failed password for invalid user ul from 13.233.112.7 port 35968 ssh2
...
2020-04-18 18:41:39
171.231.244.12 attack
Email sign in attempts
2020-04-18 18:43:21
222.186.175.23 attackbots
04/18/2020-06:47:41.141231 222.186.175.23 Protocol: 6 ET SCAN Potential SSH Scan
2020-04-18 18:48:18
114.230.202.232 attackbots
Apr 18 10:46:29 itv-usvr-01 sshd[28899]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.230.202.232  user=root
Apr 18 10:46:31 itv-usvr-01 sshd[28899]: Failed password for root from 114.230.202.232 port 37734 ssh2
Apr 18 10:50:34 itv-usvr-01 sshd[29083]: Invalid user admin from 114.230.202.232
Apr 18 10:50:34 itv-usvr-01 sshd[29083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.230.202.232
Apr 18 10:50:34 itv-usvr-01 sshd[29083]: Invalid user admin from 114.230.202.232
Apr 18 10:50:36 itv-usvr-01 sshd[29083]: Failed password for invalid user admin from 114.230.202.232 port 56000 ssh2
2020-04-18 18:43:08
70.37.61.89 attack
Wordpress malicious attack:[octablocked]
2020-04-18 18:27:17
200.124.157.22 attackbotsspam
Apr 18 05:50:43 debian-2gb-nbg1-2 kernel: \[9440816.338490\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=200.124.157.22 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=51 ID=46794 PROTO=TCP SPT=64528 DPT=80 WINDOW=16384 RES=0x00 ACK SYN URGP=0
2020-04-18 18:35:20
46.161.27.75 attackbotsspam
Apr 18 12:34:00 debian-2gb-nbg1-2 kernel: \[9465012.807227\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=46.161.27.75 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=49995 PROTO=TCP SPT=59977 DPT=8887 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-18 18:47:04
191.235.82.198 attack
Bruteforce detected by fail2ban
2020-04-18 18:38:39
198.108.67.50 attack
firewall-block, port(s): 9023/tcp
2020-04-18 18:53:06
18.27.197.252 attackbots
Automatic report - Banned IP Access
2020-04-18 18:30:34

Recently Reported IPs

104.21.53.11 1.20.219.20 104.21.53.115 104.21.53.117
104.21.53.118 104.21.53.119 104.21.53.12 104.21.53.121
104.21.53.128 104.21.53.129 104.21.53.130 255.163.45.237
104.21.53.132 104.21.53.133 104.21.53.136 104.21.53.137
104.21.53.14 104.21.53.142 104.21.53.143 104.21.53.147