We see occasional frustration, in Blogger Help Forum: Get Help with an Issue, involving broken or unreliable custom domains.
I setup the Custom Domain properly, following the Google directions.
For some of my readers, my custom domain is not opening. I can see it is going in an infinite loop in the browser - and after a long time, it's throwing errors. My domain is setup, properly. Why do I have to deal with this?
And we will investigate - and in many cases, we find the domain is setup properly.
Some custom domain published blogs have problems, which have nothing to do with the domain setup.
Some custom domain problems involve custom code, added to the template, long ago.
Not everybody is in favour of the ongoing Blogger efforts to convince blog owners to force their readers to use HTTPS / SSL, in blog access.
A number of hackers are making their websites popular, by providing code that lets blogs block forced HTTPS access - just as they provided code that blocked local country domain redirection. Some blog owners add this dodgy code, to their blogs.
This hacking lets blog owners publish their blogs, and use accessories and gadgets that only support HTTP access. Unfortunately, with third party code, you get what you get.
Some third party code, which blocks HTTPS blog access, works OK - for a while.
When a blog is published to a custom domain, redirection to "blogspot.com" causes a redirect loop - or a security check.
<script type='text/javascript'>
var blog = document.location.href.toLowerCase();
if (!blog.match(/\.blogspot\.com/)) {
blog = blog.replace(/\.blogspot\..*?\//, ".blogspot.com/ncr/");
window.location.replace(blog);
}
</script>
This is clever code, seen some time ago when used to block country local domain redirection. Then, as now, some blogs might be deleted or locked as malware hosts - or the blogs would become intermittently inaccessible.
Is the unreliability appropriate? You can add what code you like, to your blog. Eventually, what you add may cause you problems.
Some #Blogger blog owners add clever code, to block HTTPS Redirection, to their blogs. This is the same hacker provided code, used long ago to block local country domain redirection.
Like country domain redirection, the code added may work fine, for a while. Eventually, the blog will be deleted / locked for malware hosting - or will start throwing 404 errors and similar confusion.
https://productforums.google.com/forum/#!category-topic/blogger/71k8xOXxByI
A few blog owners, who publish blogs published to custom domains, are becoming impatient, waiting for Blogger Engineering to finish the Blogger upgrade to support HTTPS / SSL.
If I get a domain through Google Domains, will I be able to get HTTPS?
Unfortunately, no. HTTPS / SSL is simply not available, to blogs published to custom domains.
HTTPS is not available, for non BlogSpot published blogs.
Whether registered by eNom, GoDaddy, or Google Domains, it simply is not possible to publish a non BlogSpot URL as a supported custom domain, and make HTTPS / SSL available. CloudFlare, a supposed alternative, does not produce a supported custom domain.
A proxied CloudFlare domain looks like malicious redirection.
In some cases, a CloudFlare DNS "solution" tried by some blog owners, will look like dangerous / malicious redirection. Some blogs will show up as "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, will be classified as "Deceptive" sites.
Others will produce alarming warnings about malware.
"This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware."
Click on "Details".
Look at the warning.
Phishing sites pretend to be other websites to trick you.
And there is the typical Dig log, with a redirecting proxy service, like CloudFlare.
kireisubs.id. 300 IN A 104.27.133.198
www.kireisubs.id. 300 IN A 104.27.133.198
or
topmovies21.biz. 300 IN A 104.28.0.106
www.topmovies21.biz. 300 IN A 104.28.0.106
This is the basis for malware / phishing classification.
Any observed malware warning is generally a false positive - most custom domain published blogs do not contain malware. Even so, it's not likely that the "Deceptive site" classification will be easily corrected - or the malware warning interstitial display removed.
And this is one more blog owner, who must next be provided instruction to correct the DNS addresses.
Having corrected as instructed, DNS addresses will be asymmetrical, and righteous.
kireisubs.id. 86400 IN A 216.239.32.21
kireisubs.id. 86400 IN A 216.239.34.21
kireisubs.id. 86400 IN A 216.239.36.21
kireisubs.id. 86400 IN A 216.239.38.21
www.kireisubs.id. 86400 IN CNAME ghs.google.com.
With DNS corrected, Google shows "Not dangerous" - but the warning still displays.
"Not dangerous".
Note "CloudFlare" is still seen as the host.
You can report an error, to SafeBrowsing.
False classification now requires time consuming site review.
Use "Report Incorrect Phishing Warning", if you believe the site is safe.
Finally, get the site reviewed, from the Security Issues page in Security Console (Webmaster Tools) - Security Issues.
And while the blog remains offline, search reputation - and the owner - will suffer.
Some #Blogger blog owners want to provide blogs published to custom domains - and offer HTTPS connectivity. Since Blogger cannot provide custom domains with HTTPS right now, the blog owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks like malicious redirection - and blogs using CloudFlare are being labeled as "Deceptive" sites.
https://productforums.google.com/forum/#!category-topic/blogger/ApuJ58a4-kg
https://productforums.google.com/forum/#!category-topic/blogger/-LoJCeX6DEA
https://productforums.google.com/forum/#!category-topic/blogger/DhAFOtJFoCw
We see the signs of naivete, periodically, in Blogger Help Forum: Learn More About Blogger.
How do I require my readers to enter a password, to keep my blog safe from public view?
This blog owner does not understand the realities of setting up a private blog.
Long ago (very long ago), a computer system might have "private" files, and a shared password, known by everybody, for each file. Nowadays, a private Blogger blog uses team blog access - or team blog ownership - and each team member gets to choose her / his own Blogger account, with a password that he / she decides to use (and hopefully, remember).
Having a group shared password is fine, for a small group, where nobody leaves. What happens when somebody leaves the group?
Group shared pass codes are fine - until the group changes.
Have you ever worked in an office, where the doors are protected by a tumbler key set - or maybe combination push buttons? That's a shared password system. What happens when somebody leaves the group? Every door has to be re keyed - or the locks have to be changed.
What if the blog owner has to change the password for the blog, because somebody shared the password with a stranger - or somebody just left the group? Have you ever gotten to work, and found that your key - or assigned push button combination - doesn't work?
Have you ever had to wait for the department secretary to get to work, and give you a new key, because they changed the locks last week, while you were out of town? Have you had to anxiously search your email, looking for the message from the manager, providing the new password (here's hoping that you can get online, and your computer / phone has a freshly charged battery)?
Personal pass codes promote individual responsibility.
The personal account / password approach is so much more supportable - and it promotes responsibility. Have you ever had the manager ask everybody who came in over the weekend, and left the office in a mess?
With everybody using a common physical key, to open the door, there is no telling who comes and goes. Using individual passwords - or preferably, a card key system - you can audit employee presence, and encourage responsible attendance.
Use personal Blogger / Google accounts, for better security.
Using a personal account / password is so much better than a group shared password. Don't waste time trying to protect your blog, behind a shared password script.
Just make the blog private. Invite designated members - and let each member choose their own account / password, for blog membership.
Recently, we've had several reports from naive blog owners, with blogs locked for malware or phishing, in Blogger Help Forum: Something Is Broken.
Some owners have found accessories, such as email address collection or even a convenient login gadget, offered by helpful third parties. Installing the new gadgets, they have later received the well known (automated detection) notice, from Blogger Support.
Both third party email collection, and convenient login gadgets, are righteously classified as malware.- Email address collection, run through a third party database, can provide hackers a starting point for account and blog theft, using botnets - or the account holder may be added to email distribution lists for spammers.
- Third party login gadgets are blatant phishing tools - and can be used for immediate account and blog theft.
Neither accessories are good, for your readers.
Any such third party accessories are just hacking / phishing tools. When you install this on your blog, it becomes hacking / phishing enabled by you.
You can collect email addresses, if you wish - using a FeedBurner Email Distribution gadget, which allows your readers to subscribe to a feed from your blog. If you want to offer your readers a convenient Blogger / Google login, add an HTML gadget, targetinghttp://www.blogger.com
and let them use the standard Google "One account" login screen.
Don't be a dupe for the hackers, phishers, and spammers - keep your blog clean, and keep your blog online. The future of your blog, and your readers well being, requires your wise decisions.
>> Top
Some Blogger blog owners treat custom domain publishing, as drivers in Miami USA treat the suburban streets.
Have you ever been to Miami, Florida, USA?
Many of the suburban streets there are long, straight, and intersect at 90 degree angles. And as you get into the outer suburbs, with housing developments which (this year) may be right next to the Everglades - there will be almost no traffic, much of the day.
The major streets intersect with stop signs or traffic lights. Many of the natives blow the stop signs, run the red lights, and speed with almost reckless abandon. And auto collisions are frequent - and lawyers and police are very busy.
I car pooled with a co worker for a while, until I noticed that he drove like a native.
His justification?
My brother does this all of the time - and he never gets into an accident - and has never been stopped by the police!
One day, after work, we were getting home - and as we approached the final traffic light, the light cycled green. There was no other traffic in front, or behind.
Instead of cruising through the intersection, my bud jammed on the brakes, and came to a screeching halt. As soon as I untangled my forehead from the dashboard, I started screaming at him. His reply?
My brother lives down that street!
In Blogger Help Forum: Something Is Broken, we deal with the reckless abandon of some blog owners, setting up their custom domains.
There is much confusion, and bad advice, provided by blog owners who want to publish their blogs to custom domains - but find the official instructions to be either confining or confusing.
For every need, you will find bad advice.
- Can't buy a domain? No problem, get a free domain.
- Can't figure out the supported DNS configuration? No problem! Get the registrar to setup forwarding!!
- Can't wait for HTTPS connectivity provided by Blogger? Use proxied SSL from CloudFlare!!!
- Want to publish to the domain root ("naked" domain)? No problem! There's a great kludge for that, too!!!
There's a workaround, for every need - but how many are effective, long term?
And here in Blogger Help Forum: Something Is Broken, we see the results.
And all of these symptoms - and the frustrating secondary results - can be avoided.
If you want to setup your domain, properly - and you find the official instructions to be confining or confusing - see my tutorial here - and more recently, here.
You may, alternately, read my forum FAQ, here - or the official Blogger Help FAQ, here.
Many problems can be avoided - if you only believe. There is but one configuration, for each publishing need - if you want to avoid the problems - though some folks may be more optimistic.
- Poor search engine activity.
- Spurious malware / spam classification.
- The old "Another blog ..." / "Key already exists ...".
Or, we'll see you, in Blogger Help Forum: Something Is Broken - whether immediately, or years later.
