You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"This subtest did *not* run, because *no* route announcement was available "
1106
1106
"for any of the IP addresses."
1107
1107
1108
+
msgid"detail mail tls caa exp"
1109
+
msgstr""
1110
+
"We check if the name servers of each of your receiving mail servers (MX) contain one or more CAA records, that are syntactically valid and sufficiently protective.\n"
1111
+
"\n"
1112
+
"Certification Authority Authorisation (CAA) allows you as a DNS domain name holder to specify one or more certificate authority authorised to issue certificates for your mail server domain names.\n"
1113
+
"A certificate authority must not issue a certificate unless the certificate authority determines that the certificate request is consistent with the applicable CAA records.\n"
1114
+
"\n"
1115
+
"Note that CAA records are located during validation by walking up the DNS hierarchy until one or more records are found.\n"
1116
+
"For example, if no CAA records are found on `sub.example.nl`, `example.nl` will be queried.\n"
1117
+
"The domain were the applicable CAA records are found is shown in the table with technical details below.\n"
1118
+
"\n"
1119
+
"The verdict is good if one or more CAA records were found that all have correct syntax, and at least one of these CAA records has the `issue` tag.\n"
1120
+
"In all other cases, the test will result in a fail.\n"
1121
+
"It is not checked whether the certificate authority of the current TLS certificate matches one or more of the `issue` and `issuewild` values, i.e., whether the current certificate could be reissued at this time.\n"
1122
+
"\n"
1123
+
"If your are using the Automatic Certificate Management Environment (ACME) standard and your certificate authority supports it, we recommend you to use the parameters `validationmethods` and `accounturi` to further restrict isssuance by the authorised certificate authority. Furthermore, it is recommended to add `issuemail` and `issuevmc` with an empty `;` if you do not use certificates for S/MIME and/or BIMI respectively. Otherwise, any certificate authority is still allowed to issue these certificates for your domain, since `issue` does not cover them.\n"
1124
+
"\n"
1125
+
"We expect URLs in `iodef` to be secure (i.e. use HTTPS scheme).\n"
1126
+
"Furthermore, to prevent suppression or spoofing of CAA records we strongly recommend you to use DNSSEC, although this CAA test does not specifically test for DNSSEC.\n"
1127
+
"\n"
1128
+
"*Requirement level: Recommended*"
1129
+
1130
+
msgid"detail mail tls caa label"
1131
+
msgstr"CAA for mail server"
1132
+
1133
+
msgid"detail mail tls caa tech table"
1134
+
msgstr"Mail server|Findings"
1135
+
1136
+
msgid"detail mail tls caa verdict bad"
1137
+
msgstr"Your mail server does *not* have CAA."
1138
+
1139
+
msgid"detail mail tls caa verdict good"
1140
+
msgstr"Your mail server has a valid, sufficiently protective CAA. "
1141
+
1142
+
msgid"detail mail tls caa verdict insufficient"
1143
+
msgstr"Your mail server has a valid, but *unsufficiently* protective CAA."
1144
+
1145
+
msgid"detail mail tls caa verdict syntax-error"
1146
+
msgstr"Your mail server has an *invalid* CAA."
1147
+
1108
1148
msgid"detail mail tls cert-hostmatch exp"
1109
1149
msgstr""
1110
1150
"We check if the domain name of each of your receiving mail servers (MX) matches the domain name on the presented certificates. \n"
@@ -1859,6 +1899,86 @@ msgstr ""
1859
1899
msgid"detail tech data bogus"
1860
1900
msgstr"bogus"
1861
1901
1902
+
msgid"detail tech data caa caa-record"
1903
+
msgstr"Record: {record}"
1904
+
1905
+
msgid"detail tech data caa caa_record"
1906
+
msgstr"caa record found: {record}"
1907
+
1908
+
msgid"detail tech data caa found-host"
1909
+
msgstr"CAA found on: {host}"
1910
+
1911
+
msgid"detail tech data caa found_host"
1912
+
msgstr"found CAA on host {host}"
1913
+
1914
+
msgid"detail tech data caa invalid-flags-reserved-bits"
1915
+
msgstr"Error: Invalid reserved flags \"{flags}\""
1916
+
1917
+
msgid"detail tech data caa invalid-parameter-validation-methods"
1918
+
msgstr"Error: Invalid 'validationmethods' value \"{parameter_value}\""
1919
+
1920
+
msgid"detail tech data caa invalid-property-contactemail-value"
1921
+
msgstr"Error: Invalid 'contactemail' value \"{property_value}\""
1922
+
1923
+
msgid"detail tech data caa invalid-property-contactphone-value"
1924
+
msgstr"Error: Invalid 'contactphone' value \"{property_value}\""
1925
+
1926
+
msgid"detail tech data caa invalid-property-iodef-value"
1927
+
msgstr"Error: Invalid 'iodef' value \"{property_value}\""
1928
+
1929
+
msgid"detail tech data caa invalid-property-issuemail-value"
1930
+
msgstr"Error: Invalid 'issuemail' value \"{property_value}\""
1931
+
1932
+
msgid"detail tech data caa invalid-property-syntax"
1933
+
msgstr""
1934
+
"Error: Invalid \"{invalid_character}\" at position "
1935
+
"{invalid_character_position} in '{property_name}' value \"{property_value}\""
1936
+
" "
1937
+
1938
+
msgid"detail tech data caa invalid-reserved-property"
msgid"detail tech data caa invalid_property_issuemail_value"
1960
+
msgstr"invalid_property_issuemail_value {value}"
1961
+
1962
+
msgid"detail tech data caa invalid_property_syntax"
1963
+
msgstr""
1964
+
"invalid_property_syntax name {property_name} value {property_value} invalid "
1965
+
"character {invalid_character} at pos {invalid_character_position}"
1966
+
1967
+
msgid"detail tech data caa invalid_reserved_property"
1968
+
msgstr"invalid_reserved_property {value}"
1969
+
1970
+
msgid"detail tech data caa invalid_unknown_property"
1971
+
msgstr"invalid_unknown_property {value}"
1972
+
1973
+
msgid"detail tech data caa missing-required-property-issue"
1974
+
msgstr"Error: Required 'issue' property missing"
1975
+
1976
+
msgid"detail tech data caa not-found"
1977
+
msgstr"Error: CAA not found"
1978
+
1979
+
msgid"detail tech data caa not_found"
1980
+
msgstr"CAA not found"
1981
+
1862
1982
msgid"detail tech data good"
1863
1983
msgstr"good"
1864
1984
@@ -2652,6 +2772,45 @@ msgstr ""
2652
2772
"This subtest did *not* run, because *no* route announcement was available "
2653
2773
"for any of the IP addresses."
2654
2774
2775
+
msgid"detail web tls caa exp"
2776
+
msgstr""
2777
+
"We check if the name servers of your website domain contain one or more CAA records, that are syntactically valid and sufficiently protective.\n"
2778
+
"\n"
2779
+
"Certification Authority Authorisation (CAA) allows you as a DNS domain name holder to specify one or more certificate authorities authorised to issue certificates for your domain name.\n"
2780
+
"A certificate authority must not issue a certificate unless the CA determines that the certificate request is consistent with the applicable CAA records.\n"
2781
+
"\n"
2782
+
"Note that CAA records are located during validation by walking up the DNS hierarchy until one or more records are found.\n"
2783
+
"For example, if no CAA records are found on `sub.example.nl`, `example.nl` will be queried.\n"
2784
+
"The domain were the applicable CAA records are found is shown in the table with technical details below.\n"
2785
+
"\n"
2786
+
"The verdict is good if one or more CAA records were found that all have correct syntax, and at least one of these CAA records has the `issue` tag with a valid value.\n"
2787
+
"In all other cases, the test will result in a fail. It is not checked whether the certificate authority of the current certificate matches one or more of the `issue` and `issuewild` values, i.e., whether the current certificate could be reissued at this time.\n"
2788
+
"\n"
2789
+
"If your are using the Automatic Certificate Management Environment (ACME) standard and your certificate authority supports it, we recommend you to use the parameters `validationmethods` and `accounturi` to further restrict isssuance by the authorised certificate authority. Furthermore, it is recommended to add `issuemail` and `issuevmc` with an empty `;` if you do not use certificates for S/MIME and/or BIMI respectively. Otherwise, any certificate authority is still allowed to issue these certificates for your domain, since `issue` does not cover them.\n"
2790
+
"\n"
2791
+
"We expect URLs in `iodef` to be secure (i.e. use HTTPS scheme). \n"
2792
+
"Furthermore, to prevent suppression or spoofing of CAA records we strongly recommend you to use DNSSEC, although this CAA test does not specifically test for DNSSEC.\n"
2793
+
"\n"
2794
+
"*Requirement level: Recommended*"
2795
+
2796
+
msgid"detail web tls caa label"
2797
+
msgstr"CAA for domain"
2798
+
2799
+
msgid"detail web tls caa tech table"
2800
+
msgstr"Findings"
2801
+
2802
+
msgid"detail web tls caa verdict bad"
2803
+
msgstr"Your domain does *not* have CAA."
2804
+
2805
+
msgid"detail web tls caa verdict good"
2806
+
msgstr"Your domain has a valid, sufficiently protective CAA. "
2807
+
2808
+
msgid"detail web tls caa verdict insufficient"
2809
+
msgstr"Your domain has a valid, but *unsufficiently* protective CAA."
2810
+
2811
+
msgid"detail web tls caa verdict syntax-error"
2812
+
msgstr"Your domain has an *invalid* CAA."
2813
+
2655
2814
msgid"detail web tls cert-hostmatch exp"
2656
2815
msgstr""
2657
2816
"We check if the domain name of your website matches the domain name on the certificate. \n"
"* [RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3](https://www.rfc-editor.org/rfc/rfc8446)\n"
3873
4033
"* [RFC 5246: The Transport Layer Security (TLS) Protocol, Version 1.2](https://www.rfc-editor.org/rfc/rfc5246)\n"
4034
+
"* [RFC 9325:Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)](https://www.rfc-editor.org/rfc/rfc9325.html)\n"
3874
4035
"* [RFC 6797: HTTP Strict Transport Security (HSTS)](https://www.rfc-editor.org/rfc/rfc6797)\n"
4036
+
"\n"
4037
+
"### CAA\n"
4038
+
"* [RFC8659: DNS Certification Authority Authorization (CAA) Resource Record](https://www.rfc-editor.org/rfc/rfc8659.html)\n"
4039
+
"* [RFC8657: Certification Authority Authorization (CAA) Record Extensions for Account URI and Automatic Certificate Management Environment (ACME) Method Binding](https://www.rfc-editor.org/rfc/rfc8657.html) \n"
4040
+
"* [Baseline Requirements by Certification Authority Browser Forum](https://cabforum.org/working-groups/server/baseline-requirements/requirements/)\n"
4041
+
"* [Certification Authority Restriction Properties by IANA](https://www.iana.org/assignments/pkix-parameters/pkix-parameters.xhtml#caa-properties)\n"
4042
+
"\n"
4043
+
"### DANE\n"
3875
4044
"* [RFC 6698: The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA](https://www.rfc-editor.org/rfc/rfc6698)"
3876
4045
3877
4046
#, md-format
@@ -5367,51 +5536,3 @@ msgstr ""
5367
5536
"# Website test widget\n"
5368
5537
"Would you like visitors of your website to be able to directly start a website test? \n"
5369
5538
"Copy the HTML and CSS code from the text fields below into the source code of your website."
5370
-
5371
-
msgid"detail web tls caa label"
5372
-
msgstr"CAA web"
5373
-
5374
-
msgid"detail mail tls caa label"
5375
-
msgstr"CAA mail"
5376
-
5377
-
msgid"detail web tls caa tech table"
5378
-
msgstr"Findings"
5379
-
5380
-
msgid"detail mail tls caa tech table"
5381
-
msgstr"Mail server|Findings"
5382
-
5383
-
msgid"detail tech data caa caa_record"
5384
-
msgstr"caa record found: {record}"
5385
-
5386
-
msgid"detail tech data caa invalid_property_syntax"
5387
-
msgstr"invalid_property_syntax name {property_name} value {property_value} invalid character {invalid_character} at pos {invalid_character_position}"
5388
-
5389
-
msgid"detail tech data caa invalid_unknown_property"
5390
-
msgstr"invalid_unknown_property {value}"
5391
-
5392
-
msgid"detail tech data caa invalid_reserved_property"
5393
-
msgstr"invalid_reserved_property {value}"
5394
-
5395
-
msgid"detail tech data caa invalid_flags_reserved_bits"
5396
-
msgstr"invalid_flags_reserved_bits {value}"
5397
-
5398
-
msgid"detail tech data caa invalid_property_issuemail_value"
5399
-
msgstr"invalid_property_issuemail_value {value}"
5400
-
5401
-
msgid"detail tech data caa invalid_property_contactphone_value"
0 commit comments