Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

badssl.com goes offline due to DNS failure #500

Closed
dcheung2 opened this issue Apr 1, 2022 · 7 comments
Closed

badssl.com goes offline due to DNS failure #500

dcheung2 opened this issue Apr 1, 2022 · 7 comments

Comments

@dcheung2
Copy link

dcheung2 commented Apr 1, 2022

It is a short term service interruption or it is going to be offline forever ?

https://who.is/whois/badssl.com
show that some chances recently and the domain itself is expiring soon.

Registrar Info
NameGoogle LLC
Whois Serverwhois.google.com
Referral URLhttps://domains.google.com
StatusclientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Important Dates
Expires On 2022-04-07
Registered On 2015-04-07
Updated On 2022-03-31

@dcheung2
Copy link
Author

dcheung2 commented Apr 1, 2022

the IP 104.154.89.105 seem still up and running

@lgarron
Copy link
Collaborator

lgarron commented Apr 1, 2022

Hmm, I had no trouble accessing a few hours ago, but I can also repro now.

@christhompson
Copy link
Collaborator

christhompson commented Apr 1, 2022 via email

vadz added a commit to wxWidgets/wxWidgets that referenced this issue Apr 1, 2022
There are DNS problems with resolving it that make the tests fail, see
chromium/badssl.com#500

Require WX_TEST_WEBREQUEST_URL_SELF_SIGNED to be set to the URL to test
instead of hard-coding https://self-signed.badssl.com and don't set this
variable for now to let the tests pass.
@pbiggar
Copy link

pbiggar commented Apr 1, 2022

Confirming site is down for me on various machines with various different HttpClient (Chrome on Mac, linux curl, .NET HttpClient)

@drwetter
Copy link

drwetter commented Apr 1, 2022

I tried from several locations around the world with different upstream NS and all I got was a SERVFAIL

@pbiggar
Copy link

pbiggar commented Apr 1, 2022

It's back for me

@christhompson
Copy link
Collaborator

DNS should be back (pending any propagation delays). There might be some further hiccups later today while I work on things, but I'll double check that they're left in a working state so things don't stay down for long.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants