Cloudflare, Custom Domain Publishing, In Addition To Https
Thursday, March 31, 2016
Edit
A few spider web log owners, who reveal 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 exactly is non possible to reveal a non BlogSpot URL every bit a supported custom domain, together with brand HTTPS / SSL available. CloudFlare, a supposed alternative, does non hit a supported custom domain.
A proxied CloudFlare domain looks similar malicious redirection.
In exactly about cases, a CloudFlare DNS "solution" tried past times exactly about spider web log owners, volition await similar dangerous / malicious redirection. Some blogs volition demo upwards every bit "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, volition hold out classified every bit "Deceptive" sites.
Others volition hit alarming warnings near malware.
"This spider web log is non hosted past times Blogger together with has non been checked for spam, viruses together with other forms of malware."
Click on "Details".
Look at the warning.
And at that topographic point is the typical Dig log, amongst a redirecting proxy service, similar CloudFlare.
or
This is the footing for malware / phishing classification.
Any observed malware warning is by together with large a faux positive - most custom domain published blogs practise non comprise malware. Even so, it's non probable that the "Deceptive site" classification volition hold out easily corrected - or the malware warning interstitial display removed.
And this is i to a greater extent than spider web log owner, who must side past times side hold out provided teaching to correct the DNS addresses.
Having corrected every bit instructed, DNS addresses volition hold out asymmetrical, together with righteous.
With DNS corrected, Google shows "Not dangerous" - but the warning nonetheless displays.
"Not dangerous".
Note "CloudFlare" is nonetheless seen every bit the host.
You tin hand notice written report an error, to SafeBrowsing.
False classification straightaway requires fourth dimension consuming site review.
Use "Report Incorrect Phishing Warning", if yous believe the site is safe.
Finally, learn the site reviewed, from the Security Issues page inwards Security Console (Webmaster Tools) - Security Issues.
And spell the spider web log remains offline, search reputation - together with the possessor - volition suffer.
Some #Blogger spider web log owners desire to furnish blogs published to custom domains - together with offering HTTPS connectivity. Since Blogger cannot furnish custom domains amongst HTTPS right now, the spider web log owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks similar malicious redirection - together with 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 learn a domain through Google Domains, volition I hold out able to learn HTTPS?Unfortunately, no. HTTPS / SSL is exactly 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 exactly is non possible to reveal a non BlogSpot URL every bit a supported custom domain, together with brand HTTPS / SSL available. CloudFlare, a supposed alternative, does non hit a supported custom domain.
A proxied CloudFlare domain looks similar malicious redirection.
In exactly about cases, a CloudFlare DNS "solution" tried past times exactly about spider web log owners, volition await similar dangerous / malicious redirection. Some blogs volition demo upwards every bit "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, volition hold out classified every bit "Deceptive" sites.
Others volition hit alarming warnings near malware.
"This spider web log is non hosted past times Blogger together with has non been checked for spam, viruses together with other forms of malware."
Click on "Details".
Look at the warning.
Phishing sites pretend to hold out other websites to play tricks you.
And at that topographic point is the typical Dig log, amongst 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 footing for malware / phishing classification.
Any observed malware warning is by together with large a faux positive - most custom domain published blogs practise non comprise malware. Even so, it's non probable that the "Deceptive site" classification volition hold out easily corrected - or the malware warning interstitial display removed.
And this is i to a greater extent than spider web log owner, who must side past times side hold out provided teaching to correct the DNS addresses.
Having corrected every bit instructed, DNS addresses volition hold out asymmetrical, together with 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 nonetheless displays.
"Not dangerous".
Note "CloudFlare" is nonetheless seen every bit the host.
You tin hand notice written report an error, to SafeBrowsing.
False classification straightaway requires fourth dimension consuming site review.
Use "Report Incorrect Phishing Warning", if yous believe the site is safe.
Finally, learn the site reviewed, from the Security Issues page inwards Security Console (Webmaster Tools) - Security Issues.
And spell the spider web log remains offline, search reputation - together with the possessor - volition suffer.
Some #Blogger spider web log owners desire to furnish blogs published to custom domains - together with offering HTTPS connectivity. Since Blogger cannot furnish custom domains amongst HTTPS right now, the spider web log owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks similar malicious redirection - together with 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