Google Chrome update makes HTTPS the default for incomplete URLs

Hi Hypersot,

We have an unusually large queue of domains today, hence why. It should catch up eventually. If it still hasn't caught up in 24 hrs please let us know.

Typically though it'd be a few minutes.

We've made some improvements but the next step will be DNS wild card / resolving without the first visit. We're working on this.

matt_bodis said:

We've made some improvements but the next step will be DNS wild card / resolving without the first visit. We're working on this.

Click to expand...

Hi @matt_bodis

This is very positive news. It was in fact the main reason I stopped using the DAN-Bodis integration a while back.

matt_bodis said:

If it still hasn't caught up in 24 hrs please let us know.

Click to expand...

it's been ~2 days and domain still doesn't resolve.

@matt_bodis
4 days and still nothing. I can't imagine how much traffic is lost if this happens on other domains too.

Will DM you.

Hi Hypersot,

We're backed up by a few million domains at this time. I am sorry for not letting you know earlier. It is just a once occurence.

Once it catches up (and we implement on DNS) the issue will be resolved. Sorry for the troubles.

@matt_bodis

that's no trouble at all. The point in purchasing that domain was to have an understanding how (and, more importantly, if) the https works.

Do you plan to have a public announcement when you are fully ready to accept domains with https traffic and for them to work as intended?

thanks for replying

It def works, we now resolve HTTPS on over 9M domains.

There's various levels of integrations.

The next step is DNS which probably will solve most these issues.

Sorry for the inconvenience.

We'll announce DNS soon.

From Chromium Blog:

A safer default for navigation: HTTPS

https://blog.chromium.org/2021/03/a-safer-default-for-navigation-https.html


"For sites that don’t yet support HTTPS, Chrome will fall back to HTTP when the HTTPS attempt fails (including when there are certificate errors, such as name mismatch or untrusted self-signed certificate, or connection errors, such as DNS resolution failure)."