News for hackers. Stuff that matters.
Re:Show HN: Choose a Word by ColinWright on Sunday September 15, 2019 @06:48PM (#20979916)
Hmm:

    Warning: Potential Security Risk Ahead

    Firefox detected a potential security threat
    and did not continue to chooseaword.com.
Re:Show HN: Choose a Word by ColinWright on Monday September 16, 2019 @05:39AM (#20982407)
Ten hours later and it's loading fine. It may have been temporary, you may have fixed it, but it was real while it lasted.
Re:Show HN: Choose a Word by HenryBemis on Monday September 16, 2019 @12:02AM (#20980994)
Checking the website from my Android Firefox. NoScript and PrivacyBadger are not showing any dangerous stuff apart the typical Google analytics/tracking (which I always block). I wonder if someone from a desktop with more comprehensive tools can see if there is any sneaky frames that my tools didn't see.
Re:Show HN: Choose a Word by romes on Sunday September 15, 2019 @07:24PM (#20980062)
Hm, how would I look into that? Does it have a log you could share with me? And is anyone else getting this kind of warning?
Re:Show HN: Choose a Word by nexuist on Sunday September 15, 2019 @09:34PM (#20980479)
FWIW I'm on Firefox as well and the site loaded just fine.
Re:Show HN: Choose a Word by technion on Sunday September 15, 2019 @10:01PM (#20980564)
My "go to" answer for these issues is to run the address in virustotal.com, which will tell you about any blacklisting issues the domain may have.

In this case however, and firefox on my machine, I cannot find any issues.

Re:Show HN: Choose a Word by cellis on Sunday September 15, 2019 @11:34PM (#20980884)
Probably a DNS / dnssec / https configuration? And fwiw, doesn't happen to me.
Re:Show HN: Choose a Word by tptacek on Monday September 16, 2019 @09:02AM (#20983567)
I wonder why people on HN lately keep thinking network problems are caused by DNSSEC. Nobody uses DNSSEC (certainly this site doesn't). You can almost always assume DNSSEC isn't the problem.
Re:Show HN: Choose a Word by cellis on Thursday September 19, 2019 @01:34AM (#21013566)
Good to know, thanks! I did once have a domain where DNSSEC was misconfigured and it broke the site for certain types of queries, e.g. example.com would resolve on my ATT router but not on my LTE. And I had no idea why, but I ran a dns checker against it and it said misconfigured DNSSEC. Why don't browsers tell you when (DNSSEC misconfigured) happens?

( Honestly I still don't know why I wanted DNSSEC, but since dnsimple / google domains suggested it in their UX, I figured I should do it. )