And then use 302's for the en., nl. and www. to redirect to the apex or ipv6 accordingly.
Although this file now is used on batch, maybe also redirect batch to internet.nl and have one central file? A lot easier to manage on expiration. Dev probably should have it's own file for testing purposes.
Since these are all 301's (toolbox|emailveilig|e-mailveilig|matomo) and 302's (*dashboard), these are not strictly needed according to internet.nl:
Maybe instead of a lot of
Canonical
's: https://github.com/internetstandards/Internet.nl/blob/7bb8f53b97ffe467080884250bc0a81f029a978c/.well-known/security.txt#L4-L20 Only use:And then use 302's for the
en.
,nl.
andwww.
to redirect to the apex oripv6
accordingly.Although this file now is used on batch, maybe also redirect batch to internet.nl and have one central file? A lot easier to manage on expiration. Dev probably should have it's own file for testing purposes.
Since these are all 301's (toolbox|emailveilig|e-mailveilig|matomo) and 302's (*dashboard), these are not strictly needed according to internet.nl:
If there is a reason to be more than complete/strict
e-mailveilig.internet.nl
would be missing.Another interesting thing, the HTTPS downgrade on https://conn.internet.nl/ should not happen for sectxt:
This is HTTPS -> HTTP -> HTTPS, which is plain wrong: