WKobes

This refers to [RFC8198](https://datatracker.ietf.org/doc/html/rfc8198) instead of RFC8189.

I expect that the DNS lookup check done in the frontend fails for non-IDNA2008 IDNs. If bug #582 is addressed, this will probably cause the direct URLs to tests on...

 The missing space and semicolon seems fixed, but the disabled mode (Uitgeschakeld) is too long for a single line.

Fully agree with the last statement, I guess it depends on the perspective (security vs usability) which case is worse. I assume M3AAWG bases their policy on the security perspective...

Example where a warning/info would be nice: Use of algo 10 https://dnsviz.net/d/mijn.overheid.nl/ZKfLWg/dnssec/ https://internet.nl/site/mijn.overheid.nl/2197432/#control-panel-6

@baknu it should be noted that that info is outdated. The default is now 'strict-origin-when-cross-origin'. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

@mxsasha sorry for the late reply but multiple directories seems to be valid. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#specify_a_fallback_policy So the last policy in the list is the preferred policy (and should be tested...

This issue and #703 should be picked up as the skipped test results are sometimes misinterpreted in reports that use Internet.nl for measurements. Visually, skipped tests for 'positive' reasons (e.g.,...

For `www.werkenbijgroningen.nl`: see DigitalTrustCenter/sectxt#79 which will work again when we update the sectxt package in our next release.

> https://www.werkenbijgroningen.nl/ still breaks every time. `mail` works, `inet` fails. No error details. This is fixed in the latest sectxt release which will be included in v1.10 (https://github.com/internetstandards/Internet.nl/blob/main/Changelog.md#110-in-progress).