How can I get a digital certificate for my blog

[echoroad]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
Glitterstories.com
I ran this command:
glitterstories.com
It produced this output:
This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware.
My web server is (include version):
Blogger
The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:
Blogger
I can login to a root shell on my machine (yes or no, or I don’t know):
yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

[9peppe]

Remove your redirects and follow these instructions: https://support.google.com/blogger/answer/6284029?hl=en

[schoen]

I think there is a weird ambiguity in the DNS records for this domain. When querying repeatedly I see different addresses including

50.63.202.28
184.168.221.4
50.63.202.27
50.63.202.29

On Jürgen’s tool at https://check-your-website.server-daten.de/?q=glitterstories.com

it also saw two different IP addresses, one of which answered and one of which didn’t.

I would say that an important thing is to make sure that the DNS setting for the domain are consistent and correct, and point to the intended hosting provider and nowhere else, according to the intended hosting provider’s instructions about how to do this.

(After that, it should be useful to follow advice like @9peppe’s to make sure that the hosting provider’s HTTPS instructions are also followed.)