Cloudflare, Custom Domain Publishing, As Well As Https
Saturday, June 1, 2013
Edit
A few weblog owners, who issue blogs published to custom domains, are becoming impatient, waiting for Blogger Engineering to complete the Blogger upgrade to back upwards HTTPS / SSL.
HTTPS is non available, for non BlogSpot published blogs.
Whether registered past times eNom, GoDaddy, or Google Domains, it precisely is non possible to issue a non BlogSpot URL every bit a supported custom domain, too brand HTTPS / SSL available. CloudFlare, a supposed alternative, does non attain a supported custom domain.
A proxied CloudFlare domain looks similar malicious redirection.
In around cases, a CloudFlare DNS "solution" tried past times around weblog owners, volition await similar dangerous / malicious redirection. Some blogs volition exhibit upwards every bit "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, volition live on classified every bit "Deceptive" sites.
Others volition attain alarming warnings close malware.
"This weblog is non hosted past times Blogger too has non been checked for spam, viruses too other forms of malware."
Click on "Details".
Look at the warning.
And in that place is the typical Dig log, alongside a redirecting proxy service, similar CloudFlare.
or
This is the terra firma for malware / phishing classification.
Any observed malware warning is by too large a faux positive - most custom domain published blogs attain non incorporate malware. Even so, it's non probable that the "Deceptive site" classification volition live on easily corrected - or the malware warning interstitial display removed.
And this is i to a greater extent than weblog owner, who must side past times side live on provided didactics to correct the DNS addresses.
Having corrected every bit instructed, DNS addresses volition live on asymmetrical, too righteous.
With DNS corrected, Google shows "Not dangerous" - but the warning yet displays.
"Not dangerous".
Note "CloudFlare" is yet seen every bit the host.
You tin study an error, to SafeBrowsing.
False classification straight off requires fourth dimension consuming site review.
Use "Report Incorrect Phishing Warning", if you lot believe the site is safe.
Finally, instruct the site reviewed, from the Security Issues page inwards Security Console (Webmaster Tools) - Security Issues.
And piece the weblog remains offline, search reputation - too the possessor - volition suffer.
Some #Blogger weblog owners desire to supply blogs published to custom domains - too offering HTTPS connectivity. Since Blogger cannot supply custom domains alongside HTTPS right now, the weblog owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks similar malicious redirection - too blogs using CloudFlare are beingness labeled every bit "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
If I instruct a domain through Google Domains, volition I live on able to instruct HTTPS?Unfortunately, no. HTTPS / SSL is precisely non available, to blogs published to custom domains.
HTTPS is non available, for non BlogSpot published blogs.
Whether registered past times eNom, GoDaddy, or Google Domains, it precisely is non possible to issue a non BlogSpot URL every bit a supported custom domain, too brand HTTPS / SSL available. CloudFlare, a supposed alternative, does non attain a supported custom domain.
A proxied CloudFlare domain looks similar malicious redirection.
In around cases, a CloudFlare DNS "solution" tried past times around weblog owners, volition await similar dangerous / malicious redirection. Some blogs volition exhibit upwards every bit "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, volition live on classified every bit "Deceptive" sites.
Others volition attain alarming warnings close malware.
"This weblog is non hosted past times Blogger too has non been checked for spam, viruses too other forms of malware."
Click on "Details".
Look at the warning.
Phishing sites pretend to live on other websites to fox you.
And in that place is the typical Dig log, alongside a redirecting proxy service, similar CloudFlare.
kireisubs.id. 300 IN H5N1 104.27.133.198
www.kireisubs.id. 300 IN H5N1 104.27.133.198
or
topmovies21.biz. 300 IN H5N1 104.28.0.106
www.topmovies21.biz. 300 IN H5N1 104.28.0.106
This is the terra firma for malware / phishing classification.
Any observed malware warning is by too large a faux positive - most custom domain published blogs attain non incorporate malware. Even so, it's non probable that the "Deceptive site" classification volition live on easily corrected - or the malware warning interstitial display removed.
And this is i to a greater extent than weblog owner, who must side past times side live on provided didactics to correct the DNS addresses.
Having corrected every bit instructed, DNS addresses volition live on asymmetrical, too righteous.
kireisubs.id. 86400 IN H5N1 216.239.32.21
kireisubs.id. 86400 IN H5N1 216.239.34.21
kireisubs.id. 86400 IN H5N1 216.239.36.21
kireisubs.id. 86400 IN H5N1 216.239.38.21
www.kireisubs.id. 86400 IN CNAME ghs.google.com.
With DNS corrected, Google shows "Not dangerous" - but the warning yet displays.
"Not dangerous".
Note "CloudFlare" is yet seen every bit the host.
You tin study an error, to SafeBrowsing.
False classification straight off requires fourth dimension consuming site review.
Use "Report Incorrect Phishing Warning", if you lot believe the site is safe.
Finally, instruct the site reviewed, from the Security Issues page inwards Security Console (Webmaster Tools) - Security Issues.
And piece the weblog remains offline, search reputation - too the possessor - volition suffer.
Some #Blogger weblog owners desire to supply blogs published to custom domains - too offering HTTPS connectivity. Since Blogger cannot supply custom domains alongside HTTPS right now, the weblog owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks similar malicious redirection - too blogs using CloudFlare are beingness labeled every bit "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