3 ms·
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?
by romes 7y ago
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?
- nexuist 7y agoFWIW I'm on Firefox as well and the site loaded just fine.
- technion 7y agoMy "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.
- cellis 7y agoProbably a DNS / dnssec / https configuration? And fwiw, doesn't happen to me.
- tptacek 7y agoI 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.
- cellis 7y agoGood 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. )