d +T++s,o-&r-^-Z-*S.,~.-.0.m /?x/ /</30&60+]0E0O0X1Ox1X15!2JW2J2626$3@[3/3+383A14Bs4$4H4b$556Y6607w?7 787d8\v8d8#89/\9#9&99^:k:NQ;7;~;~W<c<x:=x=/,>J\>>1??K@@%A.AZAHB6CCDEFpFGGhH}H}I~IH JKUJHJJ/lKxKL*L>LNMKSMJMM NEN-eNN;NN(lO1OOOO|PPMQ@R*AR1lR7R6R S&S#BS(fS(SDS@S>TCRTDT:T7UMNU3U7UMV3VV)V8VVYW_WaUXRXS Y^^YpY;.ZLjZNZ[-[,E[5r[["[4[0\D\[V\\`\a2]W]X].E^9t^!^R^S#_Xw__^__B`=`I`4*aV_a;aCa6b-Qbb)bJbVc=hc=c,cd&d:d'dUemreGe/(fDXf]fGfZCgSg g:hPNhPhQhQBiOi8i8j9Vj9j9j9k>>k#}k=kk"kD!lRflPl3 mY>mYm[m[Nnvnv!owowp\pTpT:qUqUqL;rAr4r+r'+sDSs6s+sRs]Nt9t8t%u6Eu,|u,u(u4u4v$Lv9qv/v0v- w7:w.rw*wEw9xZLx`xcylyHyMyEzgdzAzJ{Y{)-|;W|<|-|?|>}}[~~Lrqp1z{j6<;SxÎH8_3*̃4,GSڄP.eWTYEI>hZOÇVNj ՈbPY%*9PhG IQN>a)?`ˌa,:{ɍE[vCՎGaGHKH>ݐ-G)c&)ޑ! < Rs>ђy_ `js [BěYauPƝa}_,ɡ|[آ&zZ4tXU]VX c;&-ĨevXoϩt?wp,u8\LTgfy(mǯ.5>d*>ΰ$ 52qh|ڱ]W]QQexNhǴ0z-Yͷ'KM4JZcڹ}>r`/f!j{!<Aɿ H,fuklHlU"VxgAUB30??#.vR5n]}C]y}DL<R9E\dmjR=(UJ,Z(31- >)K#uhaM|fJiap}q#`D7DFP\|U*W-IEP60 m<5/+,K#xALV+GV0!MRMT<C=40'$BLD4B VLmmO;_)@UJ?U)< (G)p||qXQ_~2or!o/d4A$6Md%lzxymz`zlVnk2@ DaDg)SX}h+?;k;?=##a;(Ji`,?7 MnX&DM",,>%N.t56-T>@\^IKBE7@}8E@=<~.^ie]HI lVr;6IrMB /M2}6 #*7bYw(OPJRS0B6sMOScVW&>~N7 XDBQ2 9I # / M ]% ; ; 4 u0 < U 19 ek r FD 3 U mXo;L2:TVKUWMP>@?A^B;?2_<&&L\jZ>"Ya[[]sT[e_Eb`ciA;:K=?AGF3CJMQ90, (7(`335/7e809 1A @s \ B![T!a!M"#`"S"R"F+#er#<#O$e$9 %QZ%I%)%2 &dS&{&`4''?(UX(W(d)bk)Z)=)*?g*N*J*QA+<+=+2,5A,!w,,P-@j-"-^-Q-.Q.<.</"K/]n/=/S 0>^00,0W0M91i1.1E 2f2j|2K2H33T|3B3e4=z4Z4d5Jx55j66"6$666`7Ki77.H8=w8=8I8<=9z9999 9-9!): K:l::+:):8: -;jN;;m:<A<v<a=f=lX>l>`2?w?i @>u@r@'AhABBT)C{~CCDEvEFF{%GGU!HwHIxIiIPiJgJP"KOsKRK_LvvL=L+M&MXMh/N^NcNi[O_Od%P/P[PPQ[gQQTHRR}&SWS/S@,T,mT>T"T5To2UU\$V\VSVS2WW,XjXYYhZ[Q[s\S\N\4*]e_]o]5^^j=__y9`s`'aa|Sbbfc4c"0d:Sdkd`dq[eseQAfRff`f9`g:g*g)h8*hchpheXiifi'?jxgjyjfZkXk9l^Tl\lIm:ZmHm/mVnenZvn`nK2o+~oBoLoE:p+p5p*p q&q 8q*Fq$qqqmqkrWrrmnsosiLtltm#uuBu5ub)v8G((#e)' V8; !_fm?Tq:aFBuSiN,d kI{D WR^+E[O0[0=X1p"c{?Cj*6; A!Tiq }Ph$bSY@Wg4z$MycUH: nuyo]h}Iaj*JFoL3,B42Zf L xd\Q%/MpGl@v7|'5P-s17vntVm l]&%OKJ>g+tAQU5b"rC.-H\r2k Zzw69~`><<NE|w`&3X~9e#DYK/=)_^R .x s"{domain_child}" does not exist as a DNS zone. Try to test "{domain_super}" instead."{domain_child}" is not a zone. It is an alias for "{domain_target}". Run a test for "{domain_target}" instead. Returned from name servers "{ns_list}".A CDNSKEY RRset exists, but no DNSKEY record exists. Fetched from the nameservers with IP addresses "{ns_ip_list}".A CDS RRset exists, but no DNSKEY record exists. Fetched from the nameservers with IP addresses "{ns_ip_list}".A name server should not be a recursorA single "delete" CDNSKEY record is found on the nameservers with IP addresses "{ns_ip_list}".A single "delete" CDS record is found on the nameservers with IP addresses "{ns_ip_list}".A single NS set was found ({nsname_list}).A single SOA mname value was seen ({mname}).A single SOA rname value was found ({rname}).A single SOA serial number was found ({serial}).A single SOA time parameter set was seen (REFRESH={refresh},RETRY={retry},EXPIRE={expire},MINIMUM={minimum}).A unique SOA record is returned by all nameservers of the zone.AS DiversityAS database returned no informations for IP address {ns_ip}.ASN Database error. No data to analyze for {ns_ip}.AXFR not available on nameserver {ns}.All DNSKEY algorithms used to sign the zoneAll Nameserver addresses are in the routable public addressing space.All authoritative nameservers have their IPv4 addresses in the same AS ({asn}).All authoritative nameservers have their IPv4 addresses in the same AS set ({asn_list}).All authoritative nameservers have their IPv6 addresses in the same AS ({asn}).All authoritative nameservers have their IPv6 addresses in the same AS set ({asn_list}).All keys from the DNSKEY RRset have the correct size.All name server(s) IPv4 address(es) are announced in the same IPv4 prefix.All name server(s) IPv6 address(es) are announced in the same IPv6 prefix.All nameservers reply with same IP used to query them.All nameservers succeeded to resolve to an IP address.All of the nameserver names are listed both at parent and child.All servers do not have the same CDNSKEY RRset.All servers do not have the same CDS RRset.All the IP addresses used by the nameservers are unique.All the IP addresses used by the nameservers in child are unique.All the IP addresses used by the nameservers in parent are unique.All the nameservers have SOA record.All these nameservers are confirmed to be authoritative : {nsname_list}.Ambiguous downcasing of character "{unicode_name}" in the domain name. Use all lower case instead.At least two IPv4 addresses of the authoritative nameservers are announced by different AS sets. A merged list of all AS: ({asn_list}).At least two IPv6 addresses of the authoritative nameservers are announced by different AS sets. A merged list of all AS: ({asn_list}).Authoritative answer on SOA query for "{domain}" is returned by name servers "{ns_list}".Behaviour against AAAA queryBig packet size ({size}) (try with "{command}").Both CDS and CDNSKEY RRsets are found on nameservers that resolve to IP addresses ({ns_ip_list}) but they do not match.Both IPv4 and IPv6 are disabled.Broken response from name server "{ns}" on an SOA query.CDNSKEY RRset is found on nameservers that resolve to IP addresses ({ns_ip_list}), but no CDS RRset.CDNSKEY and CDS RRsets are found on nameservers that resolve to IP addresses ({ns_ip_list}).CDS RRset is found on nameservers that resolve to IP addresses ({ns_ip_list}), but no CDNSKEY RRset.Check for invalid DNSKEY algorithmsCheck for too short or too long RRSIG lifetimesCheck for valid RSA DNSKEY key sizeChecking for revealed software versionChild does not list enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child does not list enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child does not list enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Child has extra nameserver IP address(es) not listed at parent ({ns_ip_list}).Child has nameserver(s) not listed at parent ({extra}).Child lists enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child lists enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Child lists enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Child lists no nameserver that resolves to an IPv4 address. If any were present, the minimum allowed would be {minimum}.Child lists no nameserver that resolves to an IPv6 address. If any were present, the minimum allowed would be {minimum}.Consistency between glue and authoritative dataDNS query to {ns} for {domain}/{type}/{class} failed with error: {message}DNSKEY with tag {keytag} and using algorithm {algo_num} ({algo_descr}) has a size ({keysize}) larger than the maximum one ({keysizemax}).DNSKEY with tag {keytag} and using algorithm {algo_num} ({algo_descr}) has a size ({keysize}) smaller than the minimum one ({keysizemin}).DNSKEY with tag {keytag} and using algorithm {algo_num} ({algo_descr}) has a size ({keysize}) smaller than the recommended one ({keysizerec}).DNSKEY with tag {keytag} uses unsupported algorithm {algo_num} ({algo_mnemo}) by this installation of Zonemaster. Fetched from name servers "{ns_ip_list}".DNSKEY with tag {keytag} uses unsupported algorithm {algo_num} ({algo_mnemo}) by this installation of Zonemaster. Fetched from the nameservers with IP addresses "{ns_ip_list}".DS in delegation requires signed zoneDS must match a valid DNSKEY in the child zoneDS record for the child zone found on parent nameservers with IP addresses "{ns_ip_list}".DS record for zone {domain} with keytag {keytag} was created by digest algorithm {ds_algo_num} ({ds_algo_mnemo}) which cannot be validated by this installation of Zonemaster. Fetched from the nameservers with IP addresses "{ns_ip_list}".DS record for zone {domain} with keytag {keytag} was created by digest algorithm {ds_algo_num} ({ds_algo_mnemo}) which is deprecated. Fetched from the nameservers with IP addresses "{ns_ip_list}".DS record for zone {domain} with keytag {keytag} was created by digest algorithm {ds_algo_num} ({ds_algo_mnemo}) which is not meant for DS. Fetched from the nameservers with IP addresses "{ns_ip_list}".DS record for zone {domain} with keytag {keytag} was created with an unassigned digest algorithm (algorithm number {ds_algo_num}). Fetched from the nameservers with IP addresses "{ns_ip_list}".Delegation does not list enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation does not list enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation does not list enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Delegation lists enough ({count}) nameservers that resolve to IPv4 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation lists enough ({count}) nameservers that resolve to IPv6 addresses. Lower limit set to {minimum}. Name servers: {ns_list}Delegation lists enough ({count}) nameservers. Lower limit set to {minimum}. Name servers: {nsname_list}Delegation lists no nameserver that resolves to an IPv4 address. If any were present, the minimum allowed would be {minimum}.Delegation lists no nameserver that resolves to an IPv6 address. If any were present, the minimum allowed would be {minimum}.Difference between the smaller serial ({serial_min}) and the bigger one ({serial_max}) is greater than the maximum allowed ({max_variation}).Domain name ({domain}) has a label ({label}) ending with a hyphen ('-').Domain name ({domain}) has a label ({label}) starting with an hyphen ('-').Domain name ({domain}) has a label ({label}) too long ({dlength}/{max}).Domain name ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Domain name ({domain}) has a zero-length label.Domain name ({domain}) has no label with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Domain name MX ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Domain name MX ({domain}) syntax is valid.Domain name MX ({domain}) within a 'numeric only' TLD ({tld}).Domain name has a label that is too long (more than 63 characters), "{label}".Domain name has a non-ASCII label ("{label}") which is not a valid U-label.Domain name has an ASCII label ("{label}") with a character not permitted.Domain name has repeated dots.Domain name is empty.Domain name is too long (more than 253 characters with no final dot).Domain name is too long ({fqdnlength}/{max}).Domain name starts with dot.Empty NOERROR response to SOA query was received from {ns}.Erroneous RCODE ("{rcode}") in response to an EDNS version 1 query. Fetched from the nameservers with IP addresses {ns_ip_list}Erroneous response from nameserver {ns}.Every reverse DNS entry matches name server name.Existence of CDS and CDNSKEYExistence of SOAExpected RCODE but received erroneous response to an EDNS version 1 query. Fetched from the nameservers with IP addresses {ns_ip_list}Fatal error in {module}: {msg}Flags field of DNSKEY record with tag {keytag} has not SEP bit set although DS with same tag is present in parent. Fetched from the nameservers with IP addresses "{ns_ip_list}".Flags field of DNSKEY record with tag {keytag} has not ZONE bit set although DS with same tag is present in parent. Fetched from the nameservers with IP addresses "{ns_ip_list}".Found SOA rname {rname} on following nameserver set : {ns_list}.Found illegal characters in MX ({domain}).Found illegal characters in SOA MNAME ({domain}).Found illegal characters in the domain name ({domain}).Found illegal characters in the nameserver ({domain}).Found {count} NS set(s).Found {count} SOA rname(s).Found {count} SOA serial number(s).Found {count} SOA time parameter set(s).Fully qualified master nameserver in SOAFunctional nameserver found. "A" query for www.{zname} test skipped.Glue records are consistent between glue and authoritative data.IP Prefix DiversityIP {ns_ip} in child refers to multiple nameservers ({nsname_list}).IP {ns_ip} in parent refers to multiple nameservers ({nsname_list}).IP {ns_ip} refers to multiple nameservers ({nsname_list}).IPv4 is disabled, not sending "{rrtype}" query to {ns}.IPv4 is disabled. No DNS queries are sent to these name servers: "{ns_list}".IPv4 is enabled, can send "{rrtype}" query to {ns}.IPv6 is disabled, not sending "{rrtype}" query to {ns}.IPv6 is disabled. No DNS queries are sent to these name servers: "{ns_list}".IPv6 is enabled, can send "{rrtype}" query to {ns}.If DNSKEY at child, parent should have DSIllegal character(s) found in SOA RNAME field ({rname}).In-bailiwick name server listed at parent has a mismatch between glue data at parent ({parent_addresses}) and any equivalent address record in child zone ({zone_addresses}).Inconsistent NSEC3 flag list in responses for the child zone from different name servers.Inconsistent NSEC3 iteration value in responses for the child zone from different name servers.Inconsistent hash algorithm in NSEC3 in responses for the child zone from different name servers.Inconsistent responses from zone with NSEC. Fetched from name servers "{ns_list}".Inconsistent responses from zone with NSEC3. Fetched from name servers "{ns_list}".Inconsistent salt length in NSEC3 in responses for the child zone from different name servers.Incorrect version of EDNS (expected 0) in response from {ns} on query with EDNS (version 0) asking for {domain}.It cannot be determined if the child zone is signed or not.It cannot be determined if the parent zone has DS for the child zone or not.Key with keytag {keytag} details : Size = {keysize}, Flags ({sep}, {rfc5011}).Lame delegation.Legal values for the DS hash digest algorithmLogger callback died with error: {exception}MX RRset was returned by name servers "{ns_ip_list}".MX is not an aliasMX name must have a valid hostnameMX record for the domain is not pointing to a CNAME.MX record for the domain is pointing to a CNAME.MX record presentMail targets in the MX RRset "{mailtarget_list}" returned from name servers "{ns_ip_list}".Minimum number of name serversMissing RRSIG (signature) for the NSEC record or records. Fetched from name servers "{ns_list}".Missing RRSIG (signature) for the NSEC3 record or records. Fetched from name servers "{ns_list}".Missing SOA record in NODATA response with NSEC. Fetched from name servers "{ns_list}".Missing SOA record in NODATA response with NSEC3. Fetched from name servers "{ns_list}".Misuse of '@' character in the SOA RNAME fieldMisused '@' character found in SOA RNAME field ({rname}).Module {module} finished running.Multiple NSEC records when one is expected. Fetched from name servers "{ns_list}".Multiple NSEC3 records when one is expected. Fetched from name servers "{ns_list}".Multiple NSEC3PARAM records when one is expected. Fetched from name servers "{ns_list}".NS can be resolvedNSEC record for the zone apex with incorrect type list. Fetched from name servers "{ns_list}".NSEC3 record for the zone apex with incorrect type list. Fetched from name servers "{ns_list}".Name server "{nsname}" cannot be resolved into an IP address.Name server "{ns}" does not give an authoritative answer on an SOA query.Name server "{ns}" does not respond to an SOA query.Name server "{ns}" responds with an unexpected RCODE name ("{rcode}") on an SOA query.Name server IP address "{ns_ip}" is announced by ASN {asn}.Name server IP address "{ns_ip}" is announced in prefix "{prefix}".Name server NS consistencyName server address must be globally routableName server is authoritativeName server must not point at CNAME aliasName server {ns} not adding fake delegation for domain {domain} to itself.Name servers for the child zone are inconsistent on whether the zone is signed or not.Name servers have IPv4 addresses in the following ASs: {asn}.Name servers have IPv6 addresses in the following ASs: {asn}.Name servers must have distinct IP addressesNameserver ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').Nameserver ({domain}) syntax is valid.Nameserver ({domain}) within a 'numeric only' TLD ({tld}).Nameserver {nsname} RR points to CNAME.Nameserver {nsname} has an IP address ({ns_ip}) with mismatched PTR result ({names}).Nameserver {nsname} has an IP address ({ns_ip}) with prefix {prefix} referenced in {reference} as a '{name}'.Nameserver {nsname} has an IP address ({ns_ip}) without PTR configured.Nameserver {ns} allow zone transfer using AXFR.Nameserver {ns} answered A query with an unexpected rcode ({rcode}).Nameserver {ns} answered AAAA query with an unexpected RDATA length ({length} instead of 16).Nameserver {ns} answered AAAA query with an unexpected rcode ({rcode}).Nameserver {ns} answered query for name {query_name} and type {rrtype} with RCODE {rcode}.Nameserver {ns} did not respond to a query for name {query_name} and type {rrtype}.Nameserver {ns} did not respond.Nameserver {ns} did not return "A" record(s) for {domain}.Nameserver {ns} does not give an authoritative response on an NS query over TCP.Nameserver {ns} does not give an authoritative response on an NS query over UDP.Nameserver {ns} does not give an authoritative response on an SOA query over TCP.Nameserver {ns} does not give an authoritative response on an SOA query over UDP.Nameserver {ns} does not preserve original case of the queried name ({domain}).Nameserver {ns} does not respond to NS queries over TCP.Nameserver {ns} does not respond to NS queries over UDP.Nameserver {ns} does not respond to SOA queries over TCP.Nameserver {ns} does not respond to SOA queries over UDP.Nameserver {ns} does not respond to any queries over TCP.Nameserver {ns} does not respond to any queries over UDP.Nameserver {ns} does not support EDNS0 (replies with FORMERR).Nameserver {ns} dropped AAAA query.Nameserver {ns} has one or more unknown EDNS Z flag bits set.Nameserver {ns} is a recursor.Nameserver {ns} is not a recursor.Nameserver {ns} preserves original case of queried names ({domain}).Nameserver {ns} replies on a SOA query with a different source address ({source}).Nameserver {ns} replies on an EDNS query with a truncated response without EDNS.Nameserver {ns} responded with no DNSKEY record(s).Nameserver {ns} responds to a NS query with no NS records in the answer section over TCP.Nameserver {ns} responds to a NS query with no NS records in the answer section over UDP.Nameserver {ns} responds to a SOA query with no SOA records in the answer section over TCP.Nameserver {ns} responds to a SOA query with no SOA records in the answer section over UDP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over TCP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on NS queries over UDP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over TCP.Nameserver {ns} responds with a wrong owner name ({domain_found} instead of {domain_expected}) on SOA queries over UDP.Nameserver {ns} responds with a wrong owner name ({owner} instead of {name}) on SOA queries.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over TCP.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an NS query over UDP.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over TCP.Nameserver {ns} responds with an unexpected RCODE ({rcode}) on an SOA query over UDP.Nameserver {ns} responds with multiple ({count}) SOA records on SOA queries.Nameserver {ns} response is not authoritative on {proto} port 53.Nameserver {ns} returned "A" record(s) for {domain}.Nameserver {ns} returns an upward referral.Nameservers did not respond to A query.Neither end of any label in the domain name ({domain}) has a hyphen.No CDS or CDNSKEY RRsets are found on any name server.No DNSKEYs found. Additional tests skipped.No DS record created by digest algorithm 2 (SHA-256) is present for zone {domain}.No DS record for the child zone found on parent nameservers with IP addresses "{ns_ip_list}".No IP address found for SOA 'mname' nameserver ({mname}).No MX RRset was returned by name servers "{ns_ip_list}".No SPF policy was found for {domain}.No hyphen ('-') at the start or end of the domain nameNo illegal characters in the SOA MNAME fieldNo illegal characters in the SOA RNAME fieldNo illegal characters in the domain nameNo illegal characters in the domain name ({domain}).No multiple SOA recordsNo nameserver points to CNAME alias.No nameserver was successfully resolved to an IP address.No response from nameserver {ns} on NS queries.No response from nameserver {ns} on SOA queries.No response from nameserver(s) on MX queries.No response from nameserver(s) on PTR query ({domain}).No response from nameserver(s) on SOA queries.No response from {ns} asking for {domain}.No response from {ns} when EDNS is used in query asking for {domain}.No response on MX query from name servers "{ns_ip_list}".No response or error in response on query for NSEC. Fetched from name servers "{ns_list}".No response or error in response on query for NSEC3PARAM. Fetched from name servers "{ns_list}".No response to an EDNS version 1 query. Fetched from the nameservers with IP addresses {ns_ip_list}No truncation of referralsNon-authoritative response on MX query from name servers "{ns_ip_list}".None of the following nameservers returns an upward referral : {nsname_list}.None of the nameservers listed at the parent are listed at the child.None of the zone’s name servers responded with an authoritative response to queries for SPF policies.Not enough data about {domain} was found to be able to run tests.One or more name servers do not publish the same SPF policy as the others.Out-of-bailiwick name server listed at parent with glue record has a mismatch between the glue at the parent ({parent_addresses}) and any equivalent address record found in authoritative zone ({zone_addresses}).Parent glue name records present in childParent has nameserver(s) not listed at the child ({extra}).Parent name servers are inconsistent on the existence of DS.Prefix database error for IP address {ns_ip}.Prefix database returned no information for IP address {ns_ip}.RRSIG with keytag {keytag} and covering type DNSKEY has already expired. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type DNSKEY has inception date in the future. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type SOA has already expired. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type SOA has inception date in the future. Fetched from the nameservers with IP addresses "{ns_ip_list}".RRSIG with keytag {keytag} and covering type(s) {types} expires at : {date}.RRSIG with keytag {keytag} and covering type(s) {types} has a duration of {duration} seconds, which is just fine.RRSIG with keytag {keytag} and covering type(s) {types} has a duration of {duration} seconds, which is too long.RRSIG with keytag {keytag} and covering type(s) {types} has a remaining validity of {duration} seconds, which is too long.RRSIG with keytag {keytag} and covering type(s) {types} has a remaining validity of {duration} seconds, which is too short.RRSIG with keytag {keytag} and covering type(s) {types} has already expired (expiration is: {expiration}).RRSIG(SOA) must be valid and created by a valid DNSKEYRequest to run unknown method {testcase} in module {module}.Request to run {testcase} in unknown module {module}. Known modules: {module_list}.Response from nameserver {ns} on SOA queries does not contain SOA record.Response without EDNS from {ns} on query with EDNS0 asking for {domain}.Reverse DNS entry exists for each Nameserver IP address.Reverse DNS entry exists for name server IP addressReverse DNS entry matches name server nameRoot zone with an unexpected MX RRset (non-Null MX).SOA 'expire' minimum valueSOA 'expire' value ({expire}) is higher than the minimum recommended value ({required_expire}) and not lower than the 'refresh' value ({refresh}).SOA 'expire' value ({expire}) is less than the recommended one ({required_expire}).SOA 'expire' value ({expire}) is lower than the SOA 'refresh' value ({refresh}).SOA 'minimum' maximum valueSOA 'minimum' value ({minimum}) is between the recommended ones ({lowest_minimum}/{highest_minimum}).SOA 'minimum' value ({minimum}) is higher than the recommended one ({highest_minimum}).SOA 'minimum' value ({minimum}) is less than the recommended one ({lowest_minimum}).SOA 'mname' value ({mname}) refers to a NS which is an alias (CNAME).SOA 'mname' value ({mname}) refers to a NS which is not an alias (CNAME).SOA 'refresh' minimum valueSOA 'refresh' value ({refresh}) is at least equal to the minimum recommended value ({required_refresh}).SOA 'refresh' value ({refresh}) is higher than the SOA 'retry' value ({retry}).SOA 'refresh' value ({refresh}) is less than the recommended one ({required_refresh}).SOA 'refresh' value ({refresh}) is lower than the SOA 'retry' value ({retry}).SOA 'retry' at least 1 hourSOA 'retry' lower than 'refresh'SOA 'retry' value ({retry}) is at least equal to the minimum recommended value ({required_retry}).SOA 'retry' value ({retry}) is less than the recommended one ({required_retry}).SOA MNAME ({domain}) has a label ({label}) with a double hyphen ('--') in position 3 and 4 (with a prefix which is not 'xn--').SOA MNAME ({domain}) syntax is valid.SOA MNAME ({domain}) within a 'numeric only' TLD ({tld}).SOA MNAME consistencySOA MNAME is specified as "." which usually means "no server". Fetched from name servers "{ns_ip_list}".SOA MNAME name server "{nsname}" cannot be resolved into an IP address.SOA MNAME name server "{nsname}" is not listed as NS record for the zone.SOA MNAME name server "{nsname}" resolves to a localhost IP address ({ns_ip}).SOA MNAME name server "{ns}" does not respond to an SOA query.SOA MNAME name server "{ns}" gives unexpected RCODE name ("{rcode}") in response to an SOA query.SOA MNAME name server "{ns}" is not authoritative for the zone.SOA MNAME name server "{ns}" responds to an SOA query with no SOA records in the answer section.SOA MNAME name server is "localhost", which is invalid. Fetched from name servers "{ns_ip_list}".SOA MNAME name server(s) "{ns_list}" appears to be master.SOA MNAME name server(s) "{ns_list}" do not have the highest SOA SERIAL (expected "{soaserial}" but got "{soaserial_list}")SOA RNAME consistencySOA master is not an aliasSOA serial number consistencySOA timers consistencySPF policy validationSame source addressSaw NS set ({nsname_list}) on following nameserver set : {servers}.Saw SOA serial number {serial} on following nameserver set : {ns_list}.Saw SOA time parameter set (REFRESH={refresh}, RETRY={retry}, EXPIRE={expire}, MINIMUM={minimum}) on following nameserver set : {ns_list}.Saw {count} SOA mname.Server at {server} sent {keys} DNSKEY records and {sigs} RRSIG records.Server at {server} sent {keys} DNSKEY records, and {sigs} RRSIG records.Signed child zone found on nameservers with IP addresses "{ns_ip_list}".Some name servers return an MX RRset while others return none.TCP connectivityTEST_CASE_END {testcase}.TEST_CASE_START {testcase}.Test availability of zone transfer (AXFR)Test for DNSSEC Algorithm CompletenessTest for truncated response on EDNS queryTest for undefined EDNS versionTest for unknown EDNS OPTION-CODETest for unknown EDNS flagsTest of EDNS0 supportTesting QNAME case insensitivityTesting QNAME case sensitivityThe ASN data for name server IP address "{ns_ip}" is "{data}".The Broken but functional testThe CDNSKEY RRset is a mixture between "delete" record and other records. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is not signed by the DNSKEY that the CDNSKEY record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is not signed with a DNSKEY record that a DS record points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is not signed. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY RRset is signed by RRSIG with tag {keytag} but that is not in the DNSKEY RRset. Fetched from the nameservers with P addresses "{ns_ip_list}".The CDNSKEY RRset is signed with an RRSIG with tag {keytag}, but the RRSIG does not match the DNSKEY with the same key tag. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY record with tag {keytag} does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY record with tag {keytag} has the SEP bit (bit 15) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDNSKEY record with tag {keytag} has the zone bit (bit 7) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is a mixture between "delete" record and other records. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is not signed by the DNSKEY that the CDS record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is not signed with a DNSKEY record that a DS record points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is not signed. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS RRset is signed by RRSIG with tag {keytag} but that is not in the DNSKEY RRset. Fetched from the nameservers with P addresses "{ns_ip_list}".The CDS RRset is signed with an RRSIG with tag {keytag}, but the RRSIG does not match the DNSKEY with the same key tag. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS record with tag {keytag} does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS record with tag {keytag} matches a DNSKEY record with SEP bit (bit 15) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The CDS record with tag {keytag} matches a DNSKEY record with zone bit (bit 7) unset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNS response contains an unknown EDNS option-code. Returned from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, does not contain any EDNS from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, does not contain the expected SOA record in the answer section from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, has unexpected RCODE name "{rcode}" from name servers "{ns_ip_list}".The DNS response, on query with unknown EDNS option-code, is unexpectedly not authoritative from name servers "{ns_ip_list}".The DNSKEY RRset has not been signed by any DNSKEY matched by a DS record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by algorithm {algo_num} ({algo_mnemo}) present in the DNSKEY RRset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by the DNSKEY that the CDNSKEY record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by the DNSKEY that the CDS record with tag {keytag} points to. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is not signed by the DNSKEY with tag {keytag} that the DS record refers to. Fetched from the nameservers with IP "{ns_ip_list}".The DNSKEY RRset is not signed, which is against expectation. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is signed with an RRSIG with tag {keytag} which cannot be validated by the matching DNSKEY. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY RRset is signed with an RRSIG with tag {keytag} which does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The DNSKEY record with tag {keytag} that the DS refers to does not exist in the DNSKEY RRset. Fetched from the nameservers with IP "{ns_ip_list}".The DNSKEY with tag {keytag} uses algorithm number not meant for zone signing, algorithm number {algo_num} ({algo_descr}).The DNSKEY with tag {keytag} uses algorithm number {algo_num} ({algo_descr}), which is OK.The DNSKEY with tag {keytag} uses an algorithm number {algo_num} ({algo_descr}) which is not recommended to be used.The DNSKEY with tag {keytag} uses deprecated algorithm number {algo_num} ({algo_descr}).The DNSKEY with tag {keytag} uses private algorithm number {algo_num} ({algo_descr}).The DNSKEY with tag {keytag} uses reserved algorithm number {algo_num} ({algo_descr}).The DNSKEY with tag {keytag} uses unassigned algorithm number {algo_num} ({algo_descr}).The DS record does not match the DNSKEY with tag {keytag} by algorithm or digest. Fetched from the nameservers with IP "{ns_ip_list}".The MX RRset data is inconsistent between the name servers.The NS RRset is not signed by algorithm {algo_num} ({algo_mnemo}) present in the DNSKEY RRset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The NS name must have a valid domain/hostnameThe RRSIG (signature) for the NSEC3 record cannot be verified. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC record cannot be verified. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC record has expired. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC record it not yet valid. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC3 record cannot be verified. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC3 record has expired. Fetched from name servers "{ns_list}".The RRSIG (signature) with tag {keytag} for the NSEC3 record it not yet valid. Fetched from name servers "{ns_list}".The SOA RNAME field ({rname}) is compliant with RFC2822.The SOA RNAME mail domain ({domain}) cannot be resolved to a mail server with an IP address.The SOA RNAME mail domain ({domain}) refers to an address which is an alias (CNAME).The SOA RNAME mail domain ({domain}) resolved to a mail server with localhost ({localhost}) IP address.The SOA RRset is not signed by algorithm {algo_num} ({algo_mnemo}) present in the DNSKEY RRset. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SOA RRset is not signed, which is against expectation. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SOA RRset is signed with an RRSIG with tag {keytag} which cannot be validated by the matching DNSKEY. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SOA RRset is signed with an RRSIG with tag {keytag} which does not match any DNSKEY record. Fetched from the nameservers with IP addresses "{ns_ip_list}".The SPF policy of {domain} has a syntax error. Policy retrieved from the following nameservers: {ns_ip_list}.The SPF policy of {domain} has correct syntax.The alias for "{domain}" is inconsistent between name servers.The child zone has no mail target (no MX).The child zone is unsigned, but the parent zone has DS record.The domain must have a parent domainThe domain must have at least one working name serverThe fake delegation of domain {domain} includes a name server {nsname} that cannot be resolved to any IP address.The fake delegation of domain {domain} includes an in-zone name server {nsname} without mandatory glue (without IP address).The following name server(s) are announced in the same IPv4 prefix ({ip_prefix}): "{ns_list}"The following name server(s) are announced in the same IPv6 prefix ({ip_prefix}): "{ns_list}"The following name server(s) are announced in unique IPv4 prefix(es): "{ns_list}"The following name server(s) are announced in unique IPv6 prefix(es): "{ns_list}"The following name server(s) do not respond or respond with SERVFAIL to software version query "{query_name}". Returned from name servers: "{ns_list}"The following name server(s) do not return CH class record(s) on CH class query. Returned from name servers: "{ns_list}"The following name server(s) do not reveal the software version. Returned from name servers: "{ns_list}"The following name server(s) respond to software version query "{query_name}" with string "{string}". Returned from name servers: "{ns_list}"The following name servers do not support DNSSEC or have not been properly configured. Testing for NSEC and NSEC3 has been skipped on these servers. Fetched from name servers "{ns_list}".The following name servers do not support DNSSEC or have not been properly configured. Testing for NSEC3 has been skipped on those servers. Fetched from name servers "{ns_list}".The following name servers do not use NSEC3, but others do. Testing for NSEC3 has been skipped on the following servers. Fetched from name servers "{ns_list}".The following name servers returned more than one SPF policy. Name servers: {ns_ip_list}.The following name servers returned the same SPF policy, but other name servers returned a different policy. Name servers: {ns_ip_list}.The following nameservers answer AAAA queries without problems : {ns_list}.The following nameservers failed to resolve to an IP address : {nsname_list}.The following nameservers support EDNS0 : {ns_list}.The following servers do not respond to NSEC query. Fetched from name servers "{ns_list}".The following servers give erroneous response to NSEC query. Fetched from name servers "{ns_list}".The following servers respond with NSEC3 iteration value set to zero (as recommended). Fetched from name servers "{ns_list}".The following servers respond with NSEC3 opt-out disabled (as recommended). Fetched from name servers "{ns_list}".The following servers respond with NSEC3 opt-out enabled. Fetched from name servers "{ns_list}".The following servers respond with NSEC3 opt-out enabled. The recommended practice is to disable opt-out. Fetched from name servers "{ns_list}".The following servers respond with a legal empty salt in NSEC3. Fetched from name servers "{ns_list}".The following servers respond with a legal hash algorithm in NSEC3. Fetched from name servers "{ns_list}".The following servers respond with a non-empty salt in NSEC3 ({int} octets). The recommended practice is to use an empty salt. Fetched from name servers "{ns_list}".The following servers respond with an NSEC3 record where an unassigned flag is used (bit {int}). Fetched from name servers "{ns_list}".The following servers respond with an illegal hash algorithm for NSEC3 ({algo_num}). Fetched from name servers "{ns_list}".The following servers respond with the NSEC3 iteration value {int}. The recommended practice is to set this value to 0. Fetched from name servers "{ns_list}".The name servers for parent zone "{domain_parent}" give inconsistent delegation of "{domain_child}". Returned from name servers "{ns_list}".The parent zone cannot be determined on name servers "{ns_list}".The parent zone cannot be found.The parent zone is "{domain}" as returned from name servers "{ns_list}".The returned NSEC record has an unexpected non-apex owner name. Fetched from name servers "{ns_list}".The returned NSEC3 record unexpectedly does not match the zone name. Fetched from name servers "{ns_list}".The returned NSEC3PARAM record has an unexpected non-apex owner name. Fetched from name servers "{ns_list}".The server responded with DNSKEY but not with expected NSEC or NSEC3. Fetched from name servers "{ns_list}".The smallest possible legal referral packet is larger than 512 octets (it is {size}).The smallest possible legal referral packet is smaller than 513 octets (it is {size}).The zone "{domain}" is found.The zone does not use NSEC3. Testing for NSEC3 has been skipped. Fetched from name servers "{ns_list}".The zone has NSEC records. Fetched from name servers "{ns_list}".The zone has NSEC3 records. Fetched from name servers "{ns_list}".The zone has a Null MX mixed with other MX records.The zone has a Null MX with non-zero preference.The zone is a TLD and has an unexpected MX RRset (non-Null MX).The zone is inconsistent on NSEC and NSEC3. NSEC is fetched from name servers "{ns_list_nsec}". NSEC3 is fetched from name servers "{ns_list_nsec3}".The zone is not DNSSEC signed or not properly DNSSEC signed. Testing for NSEC and NSEC3 has been skipped. Fetched from name servers "{ns_list}".The zone is not DNSSEC signed or not properly DNSSEC signed. Testing for NSEC3 has been skipped. Fetched from name servers "{ns_list}".The zone is not signed with DNSSEC.The zone responds with both NSEC and NSEC3, where only one of them is expected. Fetched from name servers "{ns_list}".There are neither DS nor DNSKEY records for the zone.There is no DNSKEY record matching the RRSIG (signature) with tag {keytag} for the NSEC record. Fetched from name servers "{ns_list}".There is no DNSKEY record matching the RRSIG (signature) with tag {keytag} for the NSEC3 record. Fetched from name servers "{ns_list}".There is no RRSIG (signature) for the NSEC record that can be verified. Fetched from name servers "{ns_list}".There is no delegation (name servers) for "{domain}" which means it does not exist as a zone.There is no misused '@' character in the SOA RNAME field ({rname}).There is no response on query with unknown EDNS option-code from name servers "{ns_ip_list}".There is no valid DNSKEY matched by any of the DS records. Fetched from the nameservers with IP addresses "{ns_ip_list}".There is no working name server for "{domain}" so it is unreachable.There must be no double hyphen ('--') in position 3 and 4 of the domain nameThis is a test of an undelegated domain so finding the parent zone is disregarded.This is a test of the root zone which has no parent zone.To check whether authoritative name servers return an upward referralUDP connectivityUnexpected DNS record in the answer section on an NSEC query. Fetched from name servers "{ns_list}".Unexpected DNS record in the answer section on an NSEC3PARAM query. Fetched from name servers "{ns_list}".Unexpected RCODE value ({rcode}) on the MX query from name servers "{ns_ip_list}".Unexpected or erroneous reply from {ns}.Unexpected response on query for "{query_name}" with query type "{rrtype}" to "{ns}".Unsigned child zone found on nameservers with IP addresses "{ns_ip_list}".Upward referral tests skipped for root zone.Using module {module} version {version}.Using prerequisite module {name} version {version}.Using version {version} of the Zonemaster engine.Valid RRSIG for DNSKEYValidate CDNSKEYValidate CDSValidate trust from DS to CDS and CDNSKEYVerify DNSSEC additional processingVerify NSEC3 parametersWhen asked for {type} records on "{domain}" with different cases, all servers do not reply consistently.When asked for {type} records on "{domain}" with different cases, all servers reply consistently.When asked for {type} records on "{domain}", nameserver {ns} returns nothing.When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns different RCODE ("{rcode1}" vs "{rcode2}").When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns different answers.When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns same RCODE "{rcode}".When asked for {type} records on "{query1}" and "{query2}", nameserver {ns} returns same answers.Wrong owner name ("{domain}") on SOA record in NODATA response with NSEC. Fetched from name servers "{ns_list}".Wrong owner name ("{domain}") on SOA record in NODATA response with NSEC3. Fetched from name servers "{ns_list}".Zone contains NSEC or NSEC3 records{child} sent a DNSKEY record, but {parent} did not send a DS record.{parent} sent a DS record, and {child} a DNSKEY record.{parent} sent a DS record, but {child} did not send a DNSKEY record.Project-Id-Version: 1.0.0 Report-Msgid-Bugs-To: PO-Revision-Date: 2024-12-10 15:07+0100 Last-Translator: milijan@arnes.si Language-Team: Register.si Language: sl MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Generator: Poedit 3.5 "{domain_child}" ne obstaja kot DNS cona. Poskusite testirati "{domain_super}"."{domain_child}" ni cona. Je alias za "{domain_target}". Zaženite test za "{domain_target}". Odgovor prejet od "{ns_list}".CDNSKEY RRset obstaja, toda DNSKEY ne obstaja. Podatki pridobljeni iz "{ns_ip_list}".CDS RRset obstaja, toda ne obstaja DNSKEY zapis. Podatki pridobljeni iz "{ns_ip_list}".Domenski strežnik ne bi smel biti rekurzivenNajden en CDNSKEY "delete" zapis na domenskih strežnikih "{ns_ip_list}".Najden en "delete CDS" zapis na domenskih strežnikih ({ns_ip_list}).Najden en nabor domenskih strežnikov ({nsname_list}).Najden en SOA MNAME ({mname}).Najden en SOA RNAME ({rname}).Najdena ena serijska številka v SOA ({serial}).Najden nabor časovnih parametrov v SOA (REFRESH={refresh}, RETRY={retry},EXPIRE={expire},MINIMUM={minimum}).Vsi Domenski strežniki so vrnili unikaten SOA zapis.Raznolikost ASAS baza ni vrnila podatka za IP naslov {ns_ip}.ASN napaka. Ni podatkov za analizo {ns_ip}.AXFR ni možen na domenskem strežniku {ns}.Vsi DNSKEY algoritmi za podpis coneVsi naslovi domenskih strežnikov so v javnem naslovnem prostoru.IPv4 naslovi vseh avtoritativnih strežnikov se nahajajo v istem AS ({asn}).IPv4 naslovi vseh avtoritativnih strežnikov se nahajajo v istem AS nizu ({asn_list}).IPv6 naslovi avtoritativnih strežnikov se nahajajo v istem AS ({asn}).IPv6 naslovi vseh avtoritativnih strežnikov se nahajajo v istem AS nizu ({asn_list}).Vsi ključi DNSKEY RRseta so pravilne velikosti.Vsi IPv4 naslovi domenskih strežnikov so oglaševani v istem IPv4 "prefixu".Vsi IPv6 naslovi domenskih strežnikov so oglaševani v istem IPv6 "prefixu".Vsi domenski strežniki se odzivajo z IP naslovom, ki je bil uporabljen v poizvedbi.Za vse domenske strežnike je bilo mogoče najti IP naslove.Domenski strežniki v starševski in podrejeni coni so enaki.CDNSKEY RRset ni enak na vseh domenskih strežnikih.CDS RRset ni enak na vseh domenskih strežnikih.Vsi IP naslovi strežnikov so unikatni.Vsi IP naslovi domenskih strežnikov v podrejeni coni so unikatni.Vsi IP naslovi domenskih strežnikov v starševski coni so unikatni.SOA zapis je prisoten na vseh domenskih strežnikih.Vsi domenski strežniki so potrjeno avtoritativni : {nsname_list}.Dvoumno zapisovanje znakov "{unicode_name}" v imenu domene. Uporabite samo male črke.Vsaj dva IPv4 naslova avtoritativnih strežnikov sta iz različnih AS. Grupiran seznam vseh AS: ({asn_list}).Vsaj dva IPv6 naslova avtoritativnih strežnikov sta iz različnih AS. Grupiran seznam vseh AS: ({asn_list}).Avtoritativni odgovor na SOA poizvedbo za "{domain}" pridobljen od "{ns_list}".Obnašanje pri AAAA poizvedbiVelik paket ({size} bajtov) (poskusi z ukazom "{command}").CDS in CDNSKEY RRseti se nahajajo na domenskih strežnikih "{ns_ip_list}", ampak se ne ujemajo.IPv6 in IPv4 sta onemogočena.Pokvarjen odgovor domenskega strežnika "{ns}" za SOA poizvedbo.CDNSKEY RRset se nahaja na domenskih strežnikih "{ns_ip_list}", ampak CDS RRseta ni.CDNSKEY in CDS RRseti se nahajajo na domenskih strežnikih "{ns_ip_list}".CDS RRset se nahaja na domenskih strežnikih "{ns_ip_list}", ampak CDNSKEY RRseta ni.Preverjanje neveljavnih DNSKEY algoritmovPreverjanje prekratkih ali predolgih RRSIG življenjskih dobPreverjanje velikosti ključa RSA DNSKEYTest objavljene verzije programske opremePodrejena cona nima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv4 naslovi. Spodnja meja nastavljena na {minimum}Podrejena cona nima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv6 naslovi. Spodnja meja nastavljena na {minimum}Podrejena cona nima dovolj ({count}) domenskih strežnikov ({nsname_list}). Spodnja meja nastavljena na {minimum}Najdeni dodatni domenski strežniki, ki niso navedeni v starševski coni ({ns_ip_list}).Podrejena cona ima domenske strežnik(e), ki ni(so) v starševski coni ({extra}).Podrejena cona ima dovolj ({count}) domenskih strežnikov z IPv4 naslovi ({ns_list}). Spodnja meja je nastavljena na {minimum}.Podrejena cona ima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv6 naslovi. Spodnja meja je nastavljena na {minimum}Podrejena cona ima dovolj({count}) domenski strežnikov ({nsname_list}). Spodnja meja nastavljena na {minimum}.Podrejena cona nima domenskih strežnikov z IPv4 naslovi. Če bi jih imela, bi jih morala imeti najmanj {minimum}.Podrejena cona nima domenskih strežnikov z IPv6 naslovi. Če bi jih imela, bi jih morala imeti vsaj {minimum}.Konsistenca med glue in avtoritativnimi podatkiDNS poizvedba za {domain}/{type}/{class} na domenskem strežniku {ns} je bila neuspešna: {message}.DNSKEY z oznako {keytag} uporablja algoritem {algo_num} ({algo_descr}) z velikostjo ključa ({keysize}), ki je večja od maksimalno dovoljene velikosti ({keysizemax}).DNSKEY z oznako {keytag} uporablja algoritem {algo_num} ({algo_descr}) z velikostjo ključa ({keysize}), ki je manjša od minimalno dovoljene velikosti ({keysizemin}).DNSKEY z oznako {keytag} uporablja algoritem {algo_num} ({algo_descr}) z velikostjo ključa ({keysize}), ki je manjša od priporočene ({keysizerec}).DNSKEY z oznako {keytag} uporablja algoritem {algo_num} ({algo_mnemo}), ki ga trenutna Zonemaster verzija ne podpira. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY z oznako {keytag} uporablja algoritem {algo_num} ({algo_mnemo}), ki ga trenutna Zonemaster verzija ne podpira. Podatki pridobljeni iz "{ns_ip_list}".Prisotnost DS zahteva podpisano conoDS se mora ujemati z veljavnim DNSKEY v podrejeni coniNajden DS zapis za podrejeno cono na starševskih strežnikih "{ns_ip_list}".DS zapis za {domain} z oznako {keytag} je bil ustvarjen z algoritmom {ds_algo_num}({ds_algo_mnemo}), ki ga trenutna Zonemaster verzija ne more preveriti. Podatki pridobljeni iz "{ns_ip_list}".DS zapis za {domain} z oznako {keytag} je bil ustvarjen z zastarelim algoritmom {ds_algo_num}({ds_algo_mnemo}). Podatki pridobljeni iz "{ns_ip_list}".DS zapis za {domain} z oznako {keytag} je bil ustvarjen z algoritmom {ds_algo_num} ({ds_algo_mnemo}), ki ni namenjen za DS podpisovanje. Podatki pridobljeni iz "{ns_ip_list}".DS zapis za {domain} z oznako {keytag} je bil ustvarjen z algoritmom ({ds_algo_num}), ki še ni v uporabi. Podatki pridobljeni iz "{ns_ip_list}".Delegacija ne ima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv4 naslovi. Spodnja meja nastavljena na {minimum}Delegacija nima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv6 naslovi. Spodnja meja nastavljena na {minimum}Delegacija nima dovolj ({count}) domenskih strežnikov ({nsname_list}). Spodnja meja nastavljena na {minimum}Delegacija ima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv4 naslovi. Spodnja meja je nastavljena na {minimum}Delegacija ima dovolj ({count}) domenskih strežnikov ({ns_list}) z IPv6 naslovi. Spodnja meja je nastavljena na {minimum}Delegacija ima dovolj ({count}) domenskih strežnikov ({nsname_list}). Spodnja meja nastavljena na {minimum}Delegacija nima domenskih strežnikov z IPv4 naslovi. Če bi jih imela, bi jih morala imeti najmanj {minimum}.Delegacija nima domenskih strežnikov z IPv6 naslovi. Če bi jih imela, bi jih morala imeti vsaj {minimum}.Razlika med najmanjšo serijsko številko({serial_min}) in največjo ({serial_max}) je večja kot je dovoljeno ({max_variation}).Domena '{domain}' vsebuje ({label}), ki se konča z vezajem '-'.Domena '{domain}' vsebuje ({label}), ki ima vezaj ('-') na začetku.Oznaka ({label}) za domeno '{domain}' je predolga ({dlength}/{max}).Domena '{domain}' vsebuje ({label}) z dvojnim vezajem ('--') na 3. in 4. mestu (predpona pa ni 'xn--').Dolžina domene '{domain}' je enaka nič.Domena '{domain}' nima dvojnega vezaja ('--') na 3. in 4. mestu (predpona pa ni 'xn--').MX za ({domain}) vsebuje ({label}), ki ima dvojni vezaj ('--') na 3. in 4. mestu, predpona pa ni 'xn--'.MX domene ({domain}) ima veljavno sintakso.MX ({domain}) je znotraj TLD, ki je 'numeric only' ({tld}).Domena ima predolgo oznako (več kot 63 znakov), "{label}".Domena ima ne-ASCII oznako ("{label}"), ki ni veljaven U-label.Domena ima oznako ASCII ("{label}") z znakom, ki ni dovoljen.Domena ima ponavljajujoče se pike.Domena je prazna.Domena je predolga (več kot 253 znakov brez končne pike).Domena je predolga ({fqdnlength}/{max}).Domena se začne s piko.Domenski strežnik {ns} je poslal prazen NOERROR odgovor na SOA poizvedbo.Napačna RCODE ("{rcode}") v odgovoru na poizvedbo EDNS verzija 1. Podatki pridobljeni iz "{ns_ip_list}".Napačen odziv iz Domenskega strežnika{ns}.Vsak povratni vnos DNS se ujema z imenom domenskega strežnika.Obstoj CDS in CDNSKEYObstoj SOAPričakovan RCODE, a prejet napačen odziv na EDNS verzija 1 poizvedbo. Podatki pridobljeni iz "{ns_ip_list}".Usodna napaka v modulu {module}: {msg}Zastavica (flags) DNSKEY zapisa z oznako {keytag} nima nastavljenega SEP bita, čeprav je DS z enako oznako prisoten v starševski coni. Podatki pridobljeni iz "{ns_ip_list}".Zastavica (flag) DNSKEY zapisa z oznako {keytag} nima nastavljenega ZONE bita, čeprav je DS z enako oznako prisoten vstarševski coni. Podatki pridobljeni iz "{ns_ip_list}".Najden SOA RNAME {rname} v naboru domenskih strežnikov : {ns_list}.Nedovoljeni znaki v MX ({domain}).Nedovoljeni znaki v SOA MNAME za ({domain}).Nedovoljeni znaki v imenu domene '{domain}'.Nedovoljeni znaki v imenu domenskega strežnika za ({domain}).Najdeno število NS nizov: ({count}).Najdeno število SOA RNAME zapisov: ({count}).Najdeno število serijskih številk v SOA: ({count}).Najdeno število časovnih parametrov v SOA ({count}).Master domenski strežnik je opredeljen v SOANajden delujoč domenski strežnik. Test "A" zapisa za www.{zname} ni bil opravljen.Glue zapisi so konsistentni med glue in avtoritativnimi podatki.Raznolikost IP prefixovIP naslov {ns_ip} v podrejeni coni se nanaša na več domenskih strežnikov ({nsname_list}).IP naslov {ns_ip} v starševski coni se nanaša na več domenskih strežnikov ({nsname_list}).IP naslov {ns_ip} se nanaša na več domenskih strežnikov ({nsname_list}).IPv4 je onemogočen, "{rrtype}" poizvedba ni bila poslana na {ns}.IPv4 je onemogočen. DNS poizvedbe niso bile poslane na: "{ns_list}".IPv4 je omogočen, lahko pošljemo "{rrtype}" poizvedbo na {ns}.IPv6 je onemogočen, "{rrtype}" ni bila poslana na {ns}.IPv6 je onemogočen. DNS poizvedbe niso bile poslane na: "{ns_list}".IPv6 je omogočen, "{rrtype}" poizvedbo lahko pošljemo na {ns}.Če je DNSKEY v podrejeni coni, mora imeti nadrejena cona DSNedovoljeni znaki v SOA RNAME polju ({rname}).Glue zapisi In-bailiwick domenskega strežnika v starševski coni ({parent_addresses}) se ne ujemajo z nobenim ekvivalentnim zapisom v podrejeni coni ({zone_addresses}).Različni domenski strežniki ne vračajo enakih zastavic v NSEC3 odgovorih za podrejeno cono.Različni domenski strežniki ne vračajo enakih iteration vrednosti v NSEC3 odgovorih za podrejeno cono.Različni domenski strežniki ne vračajo enakih hash algoritmov v NSEC3 odgovorih za podrejeno cono.Nedosledni odgovori od cone Z NSEC. Podatki pridobljeni iz: "{ns_list}".Nedosledni odgovori od cone z NSEC3. Podatki pridobljeni iz: "{ns_list}".Različni domenski strežniki ne vračajo enakih dolžin salt vrednosti v NSEC3 odgovorih za podrejeno cono.Pri poizvedbi z EDNS (verzija 0) za {domain}, domenski strežnik {ns} vrne napačno EDNS verzijo (pričakovana 0).Ni možno določiti ali je podrejena cona podpisana ali ne.Ni možno določiti ali starševska cona ima DS za podrejeno cono ali ne.Ključ z oznako {keytag}. Velikost = {keysize}, Zastavice ({sep}, {rfc5011}).Domenski strežnik nima avtoritativnih podatkov (lame delegation).Dovoljene vrednosti algoritma za DS hash digestLogger callback se je zaprl z napako: {exception}.MX RRset so vrnili domenski strežniki "{ns_ip_list}".MX ni aliasMX mora imeti veljaven hostnameMX zapis ne kaže na alias (CNAME).MX zapis za domeno kaže na alias (CNAME).MX zapis je prisotenPoštni strežniki v MX RRsetu "{mailtarget_list}" na domenskih strežnikih {ns_ip_list}.Minimalno število domenskih strežnikovManjkajoči podpisi (RRSIG) za NSEC zapise. Podatki pridobljeni iz "{ns_list}".Manjkajoči podpisi (RRSIG) za NSEC3 zapise. Podatki pridobljeni iz "{ns_list}".Manjkajoč SOA zapis v NODATA odgovoru z NSEC. Podatki pridobljeni iz "{ns_list}".Manjkajoč SOA zapis v NODATA odgovoru z NSEC3. Podatki pridobljeni iz "{ns_list}".Nepravilno uporabljen znak '@' v SOA RNAME poljuNepravilna raba znaka '@' v SOA RNAME polju ({rname}).Modul {module} je končal.Več NSEC zapisov, ko je pričakovan en. Podatki pridobljeni iz: "{ns_list}".Več NSEC3 zapisov, ko je pričakovan eden. Podatki pridobljeni iz "{ns_list}".Več NSEC3PARAM zapisov, ko je pričakovan en. Podatki pridobljeni iz: "{ns_list}".NS je možno razrešitiNSEC zapis za domeno z nepravilnim seznamom tipov. Podatki pridobljeni iz "{ns_list}".NSEC3 zapis za domeno z nepravilnim seznamom tipov. Podatki pridobljeni iz "{ns_list}".Domenski strežnik "{nsname}" se ne da razrešiti v IP naslov.Domenski strežnik "{ns}" ne vrača avtoritativnega odgovora za SOA poizvedbo.Domenski strežnik"{ns}" ne odgovarja na SOA poizvedbo.Domenski strežnik"{ns}" odgovarja z nepričakovanim RCODE ("{rcode}") za SOA poizvedbo.IP naslov domenskega strežnika "{ns_ip}" se oglaša iz AS {asn}.Številka IP domenskega strežnika "{ns_ip}" je oglaševana v prefixu "{prefix}".Konsistenca NS zapisovNaslov domenskega strežnika mora biti globalno usmerljivDomenski strežnik je avtoritativenDomenski strežnik ne sme kazati na CNAME aliasDomenski strežnik {ns} ni dodal lažne delegacije za '{domain}' samemu sebi.Domenski strežniki podrejene cone so nekonsistentni glede tega ali je cona podpisana ali ne.IPv4 naslovi domenskih strežnikov se nahajajo v AS: {asn}.IPv6 naslovi domenskih strežnikov se nahajajo v AS: {asn}.Domenski strežniki morajo imeti razočne IP nasloveDomenski strežnik ({domain}) vsebuje ({label}), ki ima dvojni vezaj ('--') na 3. in 4. mestu, predpona pa ni 'xn--'.Domenski strežnik za ({domain}) ustreza veljavnim pravilom.Domenski strežnik za ({domain}) se nahaja znotraj TLD, ki je 'numeric only' ({tld}).RR domenskega strežnika {nsname} kaže na CNAME.Domenski strežnik {nsname} ima IP-naslov ({ns_ip}), ki se ne ujema z "PTR" rezultati ({names}) zanj.Domenski strežnik {nsname} z IP-naslovom ({ns_ip}) ima prefix {prefix}, ki je naveden v {reference} kot '{name}'.Domenski strežnik {nsname} ima IP-naslov ({ns_ip}) brez "PTR" zapisa.Domenski strežnik {ns} dovoljuje prenos zone AXFR.Domenski strežnik {ns} je na A poizvedbo odgovoril z nepričakovano RCODE ({rcode}).Domenski strežnik {ns} je odgovoril na AAAA poizvedbo z nepričakovano dolžino RDATA ({length} namesto 16).Domenski strežnik {ns} je na AAAA poizvedbo odgovoril z nepričakovano RCODE ({rcode}).Domenski strežnik {ns} je na poizvedbo za {query_name} in {rrtype} odgovoril z nepričakovano RCODE ({rcode}).{ns} ne odgovarja na poizvedbe za {query_name} in {rrtype}.Domenski strežnik {ns} ni odgovoril na poizvedbo.Domenski strežnik {ns} ni vrnil "A" zapisa za '{domain}'.Domenski strežnik {ns} ne vrača avtoritativnega odgovora na NS poizvedbe prek TCP.Domenski strežnik {ns} ne vrača avtoritativnega odgovora na "NS" poizvedbe prek UDP.Domenski strežnik {ns} ne vrača avtoritativnega odgovora na SOA poizvedbe prek TCP.Domenski strežnik {ns} ne vrača avtoritativnega odgovora na "SOA" poizvedbe prek UDP.Domenski strežnik {ns} ni obdržal prvotne velikosti črk domene '{domain}'.Domenski strežnik {ns} ne odgovarja na NS poizvedbe prek TCP.Domenski strežnik {ns} ne odgovarja na "NS" poizvedbe prek UDP.Domenski strežnik {ns} ne odgovarja na SOA poizvedbe prek TCP.Domenski strežnik {ns} ne odgovarja na "SOA" poizvedbe prek UDP.Domenski strežnik {ns} ne odgovarja na nobene poizvedbe prek TCP.Domenski strežnik {ns} ne odgovarja na poizvedbe prek UDP.Domenski strežnik {ns} ne podpira EDNS0 (vrača kodo FORMERR).Domenski strežnik {ns} je zavrgel AAAA poizvedbo.Domenski strežnik {ns} ima nastavljen bit za neznan EDNS Z.Domenski strežnik {ns} je rekurziven.Domenski strežnik {ns} ni rekurziven.Domenski strežnik {ns} je obdržal prvotno velikost črk domene '{domain}'.Domenski strežnik {ns} odgovori z napačnim izvornim naslovom ({source}) pri SOA poizvedbi.Domenski strežnik {ns} vrne skrajšan (truncated) odgovor brez EDNS pri poizvedbi z EDNS.Domenski strežnik {ns} je poslal odgovor brez DNSKEY zapisov.Domenski strežnik {ns} je na NS poizvedbo odgovoril brez NS zapisov v odgovoru prek TCP.Domenski strežnik {ns} je odgovoril na "NS" poizvedbo brez NS zapisov v odgovoru prek UDP.Domenski strežnik {ns} je na SOA poizvedbo odgovoril brez SOA zapisov v odgovoru prek TCP.Domenski strežnik {ns} je odgovoril na "SOA" poizvedbo brez SOA zapisov v odgovoru prek UDP.Domenski strežnik {ns} je odgovoril z nepričakovano domeno ({domain_found}) namesto ({domain_expected}) v NS poizvedbi prek TCP.Domenski strežnik {ns} je odgovoril z nepričakovano domeno ({domain_found}) namesto {domain_expected}) za NS poizvedbe prek UDP.Domenski strežnik {ns} je odgovoril z nepričakovano domeno ({domain_found}) namesto ({domain_expected}) v SOA poizvedbi prek TCP.Domenski strežnik {ns} je odgovoril z nepričakovano domeno ({domain_found}) namesto {domain_expected}) na SOA poizvedbe prek UDP.Domenski strežnik {ns} v odgovoru na SOA poizvedbe navaja napačno domeno ({owner}, namesto {name}).Domenski strežnik {ns} je odgovoril z nepričakovano RCODE ({rcode}) na NS poizvedbe prek TCP.Domenski strežnik {ns} je odgovoril z nepričakovanim RCODE ({rcode}) na "NS" poizvedbo prek UDP.Domenski strežnik {ns} je odgovoril z nepričakovano RCODE ({rcode}) na SOA poizvedbe prek TCP.Domenski strežnik {ns} je odgovoril z nepričakovanim RCODE ({rcode}) na "SOA" poizvedbo prek UDP.Domenski strežnik {ns} je odgovoril z več SOA zapisi ({count}).{ns} je na vratih 53/{proto} podal neavtoritativen odgovor.Domenski strežnik {ns} je vrnil "A" zapise za '{domain}'.Domenski strežnik {ns} vrača usmeritev na starševsko cono.Domenski strežniki niso odgovorili na poizvedbe po "A" zapisu.Niti začetek niti konec domene '{domain}' ne vsebuje vezaja '-'.Na nobenem domenskem strežniku ni mogoče najti CDS ali CDNSKEY RRset.DNSKEY ni najden. Vsi dodatni testi so preskočeni.DS zapis ustvarjen z algoritmom 2 (SHA-256) za {domain} ne obstaja.Ni DS zapisa za podrejeno cono na starševskih strežnikih "{ns_ip_list}".Ni najdenega IP naslova za domenski strežnik v SOA zapisu 'mname' ({mname}).Domenski strežniki "{ns_ip_list}" niso vrnili MX RRseta.Za {domain} ni bila najdena nobena politika SPF.Ni vezaja ('-') na začetku ali koncu domeneNi prepovedanih znakov v SOA MNAME poljuNi prepovedanih znakov v SOA RNAME poljuDomena nima prepovedanih znakovDomena '{domain}' nima nedovoljenih znakov v imenu.Ni prisotnih več SOA zapisovNoben domenski strežnik ne kaže na alias (CNAME).Noben domenski strežnik se ni razrešil v IP naslov.Domenski strežnik {ns} ne odgovarja na "NS" poizvedbe.Domenski strežnik {ns} ne odgovarja na "SOA" poizvedbe.Domenski strežnik se ne odziva na MX poizvedbe.Ni odgovora od domenskega strežnika za "PTR" ({domain}).Domenski strežnik se ne odziva na SOA poizvedbe.Domenski strežnik {ns} ne odgovarja na poizvedbe za '{domain}'.Domenski strežnik {ns} ne odgovarja na poizvedbo po domeni '{domain}', če se uporabi EDNS.Domenski strežniki "{ns_ip_list}" ne odgovarjajo na MX poizvedbe.Ni odgovora ali napaka v odgovoru na poizvedbo za NSEC. Podatki pridobljeni iz "{ns_list}".Ni odgovora ali napaka v odgovoru na poizvedbo za NSEC3PARAM. Podatki pridobljeni iz "{ns_list}".Ni odziva na EDNS verzija 1 poizvedbo. Podatki pridobljeni iz "{ns_ip_list}".Ni dovoljeno skrajševanje referencDomenski strežniki "{ns_ip_list}" so dali neavtoritativen odgovor na MX poizvedbo.Noben od naslednjih domenski strežnikov ne vrača upward referral: {nsname_list}.Noben od domenskih strežnikov v starševski coni ni v podrejeni coni.Nobeden od strežnikov za domeno ne odgovori z avtoritativnim odgovorom na poizvedbe za politike SPF.Premalo informacij za '{domain}', da bi lahko zagnali teste.Eden ali več domenskih strežnikov ne objavlja enake politike SPF, kot ostali.Glue zapisi out-of-bailiwick domenskega strežnika, ki je v starševski coni ({parent_addresses}), se ne ujemajo z nobenimi ekvivalentnimi zapisi v avtoritativni coni ({zone_addresses}).Glue zapisi starševske cone so prisotni v podrejeni coniStarševska cona ima domenske strežnik(e), ki ni(so) v podrejeni coni ({extra}).Podatki na starševskih strežnikih so nekonsistentni glede obstoja "DS".Napaka baze predpon za IP naslov {ns_ip}.Baza predpon nima podatka za IP številko {ns_ip}.RRSIG z oznako {keytag}, ki zajema DNSKEY zapise, je potekel. Podatki pridobljeni iz "{ns_ip_list}".RRSIG z oznako {keytag}, ki zajema DNSKEY zapise, ima datum začetka v prihodnosti. Podatki pridobljeni iz "{ns_ip_list}".RRSIG z oznako {keytag}, ki zajema SOA zapis, je potekel. Podatki pridobljeni iz "{ns_ip_list}".RRSIG z oznako {keytag}, ki zajema SOA zapis, ima datum začetka veljavnosti v prihodnosti. Podatki pridobljeni iz "{ns_ip_list}".RRSIG z oznako {keytag}, ki pokriva "{types}" poteče : {date}.RRSIG z oznako {keytag}, ki pokriva "{types}" traja {duration} sekund, kar je v redu.RRSIG z oznako {keytag}, ki pokriva "{types}" traja {duration} sekund, kar je predolgo.RRSIG z oznako {keytag}, ki pokriva "{types}" ima veljavnost še {duration} sekund, kar je predolgo.RRSIG z oznako {keytag}, ki pokriva "{types}" ima veljavnost še{duration} sekund, kar je premalo.RRSIG z oznako {keytag}, ki pokriva "{types}" je že potekel (datum poteka: {expiration}).RRSIG(SOA) mora biti veljaven in ustvarjen z veljavnim DNSKEYZahteva za izvedno neznane metode {testcase} v modulu {module}.Zahteva se {testcase} v neznanem modulu {module}. Znani moduli: {module_list}.Odgovor domenskega strežnika {ns} na SOA poizvedbo ne vsebuje SOA zapisa.Domenski strežnik {ns} je odgovoril brez EDNS pri poizvedbi z EDNS0 za {domain}.Vsi IP-naslovi domenski strežniki imajo povratni zapis DNS.Za IP-naslov domenskega strežnika obstaja povratni DNS zapisPovratni vnos DNS se ujema z domenskim strežnikomRoot cona z nepričakovanim MX RRsetom (non-Null MX).Minimalna vrednost 'expire' v SOASOA 'expire' vrednost ({expire}) je višja od priporočene ({required_expire}) in ni nižja od 'refresh' vrednosti ({refresh}).SOA 'expire' vrednost ({expire}) je manjša od priporočene ({required_expire}).SOA 'expire' ({expire}) je manjši od SOA 'refresh' ({refresh}).Maksimalna vrednost 'expire' v SOASOA 'minimum' vrednost ({minimum}) je med priporočenimi ({lowest_minimum}/{highest_minimum}).SOA 'minimum' vrednost ({minimum}) je večja od priporočene ({highest_minimum}).SOA 'minimum' vrednost ({minimum}) je manjša od priporočene ({lowest_minimum}).SOA 'mname' ({mname}) se nanaša na NS, ki je alias (CNAME).SOA 'mname' ({mname}) se nanaša na NS, ki ni alias (CNAME).Minimalna vrednost 'refresh' v SOASOA 'refresh' vrednost ({refresh}) je vsaj enaka minimalno priporočeni ({required_refresh}).SOA 'refresh' ({refresh}) je večji od SOA 'retry' ({retry}).SOA 'refresh' vrednost ({refresh}) je manjša od priporočene ({required_refresh}).SOA 'refresh' ({refresh}) je manjši od SOA 'retry' ({retry}).SOA 'retry' vsaj 1 uroVrednost SOA 'retry' je manjša od 'refresh'SOA 'retry' vrednost ({retry}) je vsaj enaka minimalno priporočeni ({required_retry}).SOA 'retry' vrednost ({retry}) je manjša od priporočene ({required_retry}).SOA MNAME ({domain}) vsebuje ({label}) z dvojnim vezajem ('--') na 3. in 4. mestu, predpona pa ni 'xn--'.SOA MNAME za ({domain}) ima veljavno sintakso.SOA MNAME za ({domain}) je znotraj TLD, ki je 'numeric only' ({tld}).Konsistenca SOA MNAMESOA MNAME je določen kot ".", kar ponavadi pomeni brez strežnika. Podatki pridobljeni iz "{ns_ip_list}".SOA MNAME domenskega strežnika "{nsname}" se ne da razrešiti v IP naslov.SOA MNAME domenski strežnik ({nsname}) ni naveden kot NS zapis za cono.SOA MNAME domenski strežnik "{nsname}" se razreši v localhost IP naslov ({ns_ip}).SOA MNAME domenski strežnik "{ns}" ne odgovarja na SOA poizvedbe.SOA MNAME domenski strežnik "{ns}" vrača nepričakovan RCODE ({rcode}) v odgovoru na SOA poizvedbo.SOA MNAME domenski strežnik "{ns}" ni avtoritativen za cono.SOA MNAME domenski strežnik "{ns}" odgovarja na SOA poizvedbe brez SOA zapisa v odgovoru.SOA MNAME domenski strežnik je "localhost", kar ni veljavno. Podatki pridobljeni iz "{ns_ip_list}".SOA MNAME domenski strežniki "{ns_list}" so videti kot master strežniki.SOA MNAME domenski strežnik(i) "{ns_list}" nima(jo) najvišje SOA serijske številke (pričakovana serijska: "{soaserial}"; serijska v odgovoru: "{soaserial_list}").Konsistenca SOA RNAMESOA master ni aliasKonsistenca SOA serijske številkeKonsistenca SOA časovnih intervalovValidacija politike SPFEnak izvorni naslovNabor domenskih strežnikov ({nsname_list}) je opredeljen na naslednjih strežnikih : {servers}.SOA serijska številka {serial} v naboru domenskih strežnikov : {ns_list}.Nabor SOA časovnih parametrov (REFRESH={refresh}, RETRY={retry}, EXPIRE={expire}, MINIMUM={minimum}) na naboru domenskih strežnikov : {ns_list}.Najdeno število SOA MNAME zapisov: ({count}).{server} je poslal (DNSKEY) {keys} in podpise (RRSIG) {sigs}.{server} je poslal (DNSKEY) {keys} in podpise (RRSIG) {sigs}.Podpisana podrejena cona najdena na domenskih strežnikih "{ns_ip_list}".Nekateri domenski strežniki vračajo MX RRset, drugi pa ne.Povezljivost TCPTEST_CASE_END {testcase}.TEST_CASE_START {testcase}.Test prenosa cone (AXFR)Test popolnosti DNSSEC algoritmaTest za skrajšane odgovore na EDNS poizvedbeTest za nedefinirane verzije EDNSTest za neznane EDNS OPTION-CODETest za neznane EDNS zastaviceTest podpore EDNS0Test neobčutljivosti na velike črke QNAMETest občutljivosti na velike črke QNAMEASN podatki domenskega strežnika "{ns_ip}" so "{data}".Pokvarjen toda funkcionalen testCDNSKEY RRset je mešanica med "delete" zapisom in ostalimi zapisi. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY RRset ni podpisan z DNSKEY-jem na katerega kaže CDNSKEY zapis z oznako {keytag}. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY RRset ni podpisan z DNSKEY zapisom na katerega kaže DS zapis. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY RRset ni podpisan. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY RRset je podpisan z RRSIG z oznako {keytag}, kar pa ni v DNSKEY RRsetu. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY RRset je podpisan z RRSIG z oznako {keytag}, toda RRSIG se ne ujema z DNSKEY-jem z enako oznako. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY z oznako {keytag} se ne ujema z nobenim DNSKEY zapisom. Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY zapis z oznako {keytag} nima nastavljenega SEP bita (bit 15). Podatki pridobljeni iz "{ns_ip_list}".CDNSKEY zapis z oznako {keytag} nima nastavljenega zone bita (bit 7). Podatki pridobljeni iz "{ns_ip_list}".CDS RRset je mešanica "delete" zapisa in drugih zapisov. Podatki pridobljeni iz "{ns_ip_list}".CDS RRset ni podpisan z DNSKEY-em na katerega kaže CDS zapis z oznako {keytag}. Podatki pridobljeni iz "{ns_ip_list}".CDS RRset ni podpisan z DNSKEY zapisom na katerega kaže DS zapis. Podatki pridobljeni iz "{ns_ip_list}".CDS RRset ni podpisan. Podatki pridobljeni iz "({ns_ip_list}".CDS RRset je podpisan z RRSIG z oznako {keytag}, kar pa ni v DNSKEY RRsetu. Podatki pridobljeni iz ({ns_ip_list}).CDS RRset je podpisan z RRSIG z oznako {keytag}, toda RRSIG se ne ujema z DNSKEY-em z enako oznako. Podatki pridobljeni iz "{ns_ip_list}".CDS zapis z oznako {keytag} se ne ujema z nobenim DNSKEY zapisom. Podatki pridobljeni iz ({ns_ip_list}).CDS zapis z oznako {keytag} se ujema z DNSKEY zapisom, ki nima nastavljenega SEP bita (bit 15). Podatki pridobljeni iz "{ns_ip_list}".CDS zapis z oznako {keytag} se ujema z DNSKEY zapisom, ki nima nastavljenega zone bita (bit 7). Podatki pridobljeni iz "{ns_ip_list}".DNS odgovor vsebuje neznano EDNS option-code. Podatki pridobljeni iz "{ns_ip_list}".Seznam domenskih strežnikov, kjer v DNS odgovoru na poizvedbo z neznano EDNS option-code, ni nobenega EDNS "{ns_ip_list}".Seznam domenskih strežnikov, kjer v DNS odgovoru na poizvedbo z neznano EDNS option-code, ni nobenega pričakovanega SOA zapisa. "{ns_ip_list}".Seznam domenskih strežnikov, kjer so v DNS odgovoru na poizvedbo z neznano EDNS option-code, nepričakovani RCODE "{rcode}". "{ns_ip_list}".Seznam domenskih strežnikov, kjer je DNS odgovor na poizvedbo z neznano EDNS option-code, nepričakovano ne avtoritativen. "{ns_ip_list}".DNSKEY RRset ni bil podpisan z nobenim DNSKEY-em, ki bi se ujemal z DS zapisom. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset ni podpisan z algoritmom {algo_num} ({algo_mnemo}), ki je prisoten v DNSKEY RRsetu. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset ni podpisan z DNSKEY-jem na katerega kaže CDNSKEY zapis z oznako {keytag}. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset ni podpisan z DNSKEY-jem na katerega kaže CDS zapis z oznako {keytag}. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset ni podpisan z DNSKEY-em z oznako {keytag} na katerega se DS zapis sklicuje. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset ni podpisan, kar ni pričakovano. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset je podpisan z RRSIG z oznako {keytag}, ki ga ni mogoče validirati z ustreznim DNSKEY-em. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY RRset je podpisan z RRsig z oznako {keytag}, ki ne ustreza nobenemu DNSKEY zapisu. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY z oznako {keytag} na katerega se sklicuje DS, ne obstaja v DNSKEY RRsetu. Podatki pridobljeni iz "{ns_ip_list}".DNSKEY z oznako {keytag} uporablja algoritem, ki ni namenjen podpisovanju cone {algo_num} ({algo_descr}).DNSKEY z oznako {keytag} uporablja veljaven algoritem {algo_num} ({algo_descr}).DNSKEY z oznako {keytag} uporablja algoritem, ki ni priporočljiv za uporabo {algo_num} ({algo_descr}).DNSKEY z oznako {keytag} uporablja zastarel algoritem {algo_num} ({algo_descr}).DNSKEY z oznako {keytag} uporablja zasebni algoritem {algo_num} ({algo_descr}).DNSKEY z oznako {keytag} uporablja rezerviran algoritem {algo_num} ({algo_descr}).DNSKEY z oznako {keytag} uporablja nepodprt algoritem (ni v veljavi) {algo_num} ({algo_descr}).DS zapis se ne ujema z DNSKEY-em z oznako {keytag} v algoritmu ali v izvlečku. Podatki pridobljeni iz "{ns_ip_list}".MX zapisi niso enaki na vseh domenskih strežnikih za domeno.NS RRset ni podpisan z algoritmom {algo_num} ({algo_mnemo}), ki je prisoten v DNSKEY RRsetu. Podatki pridobljeni iz "{ns_ip_list}".NS mora imeti veljavno domeno/hostnamePodpisa (RRSIG) za NSEC3 zapis ni mogoče preveriti. Podatki pridobljeni iz "{ns_list}".RRSIG (podpis) z oznako {keytag} za NSEC zapis ni mogoče preveriti. Podatki pridobljeni iz "{ns_list}".RRSIG (podpis) z oznako {keytag} za NSEC zapis je potekel. Podatki pridobljeni iz "{ns_list}".RRSIG (podpis) z oznako {keytag} za NSEC zapis ni še veljaven. Podatki pridobljeni iz "{ns_list}".RRSIG (podpis) z oznako {keytag} za NSEC3 zapis ni mogoče preveriti. Podatki pridobljeni iz "{ns_list}".RRSIG (podpis) z oznako {keytag} za NSEC3 zapis je potekel. Podatki pridobljeni iz "{ns_list}".RRSIG (podpis) z oznako {keytag} za NSEC3 zapis ni še veljaven. Podatki pridobljeni iz "{ns_list}".SOA RNAME ({rname}) polje je skladno z RFC2822.Domeno ({domain}) v polju SOA RNAME ni možno razrešiti v poštni strežnik z IP naslovom.Domena ({domain}) iz SOA RNMAME polja se nanaša na naslov, ki je alias (CNAME).Domena ({domain}) iz SOA RNAME polja se je razrešila v localhost ({localhost}) IP naslov.SOA RRset ni podpisan z algoritmom {algo_num} ({algo_mnemo}), ki je prisoten v DNSKEY RRsetu. Podatki pridobljeni iz "{ns_ip_list}".SOA RRset ni podpisan, kar je nepričakovano. Podatki pridobljeni iz "{ns_ip_list}".SOA RRset je podpisan z RRSIG z oznako {keytag}, ki se ga ne da preveriti z ustreznim DNSKEY-em. Podatki pridobljeni iz "{ns_ip_list}".SOA RRset je podpisan z RRSIG z oznako {keytag}, ki ne ustreza nobenemu DNSKEY zapisu. Podatki pridobljeni iz "{ns_ip_list}".Politika SPF za {domain} ima sintaktično napako. Politika pridobljena iz {ns_ip_list}.Politika SPF za {domain} ima pravilno sintakso.Alias za "{domain}" je nekonsistenten med domenskimi strežniki.Podrejena cona nima cilja za pošto (ni MX).Podrejena cona ni podpisana, starševska cona pa ima DS zapis.Domena mora imeti nadrejeno domenoDomena mora imeti vsaj en delujoč domenski strežnikSimulirana delegacija za '{domain}' vsebuje domenski strežnik {nsname}, ki se ga ne da razrešiti v IP naslov.Simulirana delegacija {domain} vključuje domenski strežnik znotraj domene {nsname}, ki nima obveznega lepila (brez IP naslova).Navedeni domenski strežniki so oglaševani v istem IPv4 prefixu ({ip_prefix}) : "{ns_list}"Navedeni domenski strežniki so oglaševani v istem IPv6 prefixu ({ip_prefix}) : "{ns_list}"Navedeni domenski strežniki so oglaševani v različnih IPv4 prefixih: "{ns_list}"Navedeni domenski strežniki so oglaševani v različnih IPv6 prefixih: "{ns_list}"Naslednji domenski strežniki se ne odzivajo ali se odzovejo z SERVFAIL na poizvedbo "{query_name}" za verzijo programske opreme. Podatki pridobljeni iz: "{ns_list}"Naslednji doemnski strežniki ne vrnejo zapisov CH razreda na poizvedbo za zapise CH razreda. Podatki pridobljeni iz: "{ns_list}"Naslednji domenski strežniki ne razkrijejo verzije programske opreme. Podatki pridobljeni iz: "{ns_list}"Naslednji domenski strežniki se odzovejo na poizvedbo "{query_name}" za verzijo programske opreme z "{string}". Podatki pridobljeni iz: "{ns_list}"Naslednji domenski strežniki ne podpirajo DNSSEC ali pa niso pravilno konfigurirani. NSEC3 in NSEC3 testiranje za te strežnike je bilo preskočeno. Podatki pridobljeni iz "{ns_list}".Naslednji domenski strežniki ne podpirajo DNSSEC ali pa niso pravilno konfigurirani. NSEC3 testiranje za te strežnike je bilo preskočeno. Podatki pridobljeni iz "{ns_list}".Naslednji domenski strežniki ne uporabljajo NSEC3, za razliko od ostalih. NSEC3 testiranje za te strežnike je bilo preskočeno. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki ({ns_ip_list}) so vrnili več kot eno politiko SPF.Naslednji domenski strežniki ({ns_ip_list}) so vrnili eno politiko SPF, ampak ostali pa so odgovorili z drugačno.Naslednji domenski strežniki brez težav odgovarjajo na AAAA poizvedbe: {ns_list}.Domenski strežniki, kjer ni uspelo razreševanje v IP naslove: {nsname_list}.Domenski strežniki, ki podpirajo EDNS0 : {ns_list}.Naslednji domenski strežniki se ne odzivajo na NSEC3 poizvedbe. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki vračajo napačen odgovor na NSEC poizvedbo. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki odgovorijo z iteration vrednostjo 0 (kot je piporočeno) v NSEC3. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki odgovorijo z onemogočenim NSEC3 opt-out (kot je priporočeno). Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki odgovorijo z omogočenim NSEC3 opt-out. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki odgovorijo z omogočenim NSEC3 opt-out. Priporočeno je opt-out onemogočiti. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki odgovorijo z dovoljeno prazno salt vrednostjo v NSEC3. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki odgovorijo z dovoljenim hash algoritmom v NSEC3. Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki na poizvedbo vračajo NSEC3 salt vrednost {int}. Priporočena vrednost je prazen niz '-'. Podatki pridobljeni iz : "{ns_list}".Naslednji domenski strežniki vračajo NSEC3 zapis, kjer je uporabljena nedodeljena zastavica(bit{int}). Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki vračajo nepravilne hash vrednosti za NSEC3 ({algo_num}). Podatki pridobljeni iz: "{ns_list}".Naslednji domenski strežniki na poizvedbo vračajo NSEC3 iteration vrednost {int}. Priporočena vrednost je 0. Podatki pridobljeni iz : "{ns_list}".Domenski strežniki starševske cone "{domain_parent}" kažejo na nekonsistentno delegacijo za "{domain_child}". Podatki pridobljeni od "{ns_list}".Ni možno ugotoviti starševske cone na "{ns_list}".Starševske cone ni mogoče najti.Starševska cona je "{domain}", kot poročajo "{ns_list}".Vrnjen NSEC zapis ima drugačno domeno, kot je bila domena v poizvedbi. Podatki pridobljeni iz "{ns_list}".Vrnjen NSEC3 zapis se nepričakovano ne ujema z imenom cone. Podatki pridobljeni iz "{ns_list}".Vrnjen NSEC3PARAM zapis ima drugačno domeno, kot je bila domena v poizvedbi. Podatki pridobljeni iz "{ns_list}".Domenski strežnik odgovori z DNSKEY, ampak ne z pričakovanim NSEC ali NSEC3. Podatki pridobljeni iz: "{ns_list}".Najmanjši referral paketek je večji od 512 bajtov (velikost paketka je {size}).Najmanjši referral paketek je manjši od 513 bajtov (velikost paketka je {size}).Cona "{domain}" najdena.Cona ne uporablja NSEC3. Testiranje za NSEC3 je preskočeno. Podatki pridobljeni iz "{ns_list}".Cona ima NSEC zapise. Podatki pridobljeni iz "{ns_list}".Cona ima NSEC3 zapise. Podatki pridobljeni iz "{ns_list}".Cona ima "null MX" in še druge MX zapise.Cona ima "null MX" s preferenco, ki ni 0.Cona je TLD in ima nepričakovan MX RRset (non-Null MX).Nekonsistentni zapisi za NSEC in NSEC3. NSEC zapisi pridobljeni iz "{ns_list_nsec}". NSEC3 zapisi pridobljeni iz "{ns_list_nsec3}".Cona ni (pravilno) DNSSEC podpisana. Testa za NSEC in NSEC3 sta izpuščena. Zapisi pridobljeni iz "{ns_list}".Cona ni (pravilno) DNSSEC podpisana. Test za NSEC3 je izpuščen. Zapisi pridobljeni iz "{ns_list}".Cona ni DNSSEC podpisana.Cona odgovori z NSEC in NSEC3 zapisoma, ko je pričakovan le eden. Podatki pridobljeni iz "{ns_list}".Ni niti DS niti DNSKEY zapisov za cono.DNSKEY zapisa, ki bi se ujemal z RRSIG (podpis) z oznako {keytag} za NSEC zapis, ni. Podatki pridobljeni iz "{ns_list}".DNSKEY zapisa, ki bi se ujemal z RRSIG (podpis) z oznako {keytag} za NSEC3 zapis, ni. Podatki pridobljeni iz "{ns_list}".Ni Podpisa (RRSIG) za NSEC zapis, ki bi ga bilo mogoče preveriti. Podatki pridobljeni iz "{ns_list}".Ni delegacije (domenskih strežnikov) za "{domain}", kar pomeni, da ne obstaja kot cona.Ni nepravilne rabe znaka '@' v SOA RNAME polju ({rname}).Domenski strežniki, ki se ne odzovejo na poizvedbo z neznano EDNS option-code "{ns_ip_list}".Ni veljavnega DNSKEY-a, ki bi se ujemal z DS zapisom. Podatki pridobljeni iz "{ns_ip_list}".Ni delujočega domenskega strežnika za "{domain}", zato je nedosegljiva.Dvojni vezaj ('--') ne sme biti na 3. in 4. mestu v domeniV tem testu ne iščemo starševske cone, ker je to 'undelegated' test.To je test root cone, ki nima starševske cone.Test, ki preverja, če avtoritativni strežniki vračajo usmeritev na starševsko conoPovezljivost UDPNepričakovan DNS zapis v odgovoru na NSEC poizvedbo. Podatki pridobljeni iz: "{ns_list}".Nepričakovan DNS zapis v odgovoru na NSEC3PARAM poizvedbo. Podatki pridobljeni iz: "{ns_list}".Nepričakovana RCODE vrednost ({rcode}) pri MX poizvedbi na "{ns_ip_list}".Nepričakovan ali napačen odgovor od {ns}.Nepričakovan odgovor na "{query_name}" tipa "{rrtype}" na "{ns}".Nepodpisana podrejena cona najdena na domenskih strežnikih "{ns_ip_list}".Testi za starševsko cono niso bili opravljeni, ker gre za root cono.Uporaba modula {module}, verzije {version}.Uporaba zahtevanega modula {name}, verzije {version}.Uporablja se Zonemaster verzija {version}.Veljaven RRSIG za DNSKEYValidiraj CDNSKEYValidiraj CDSValidiraj zaupanje od DS do CDS in CDNSKEYPreverjanje dodatnih DNSSEC podatkovPreveri NSEC3 parametreDomenski strežniki odgovarjajo nedosledno, ko različni testi delajo poizvedbe za {type} zapise na {domain}.Domenski strežniki odgovarjajo dosledno, ko različni testi delajo poizvedbe za {type} zapise na {domain}.Pri poizvedbi za {type} zapis na "{domain}", domenski strežnik {ns} ni vrnil odgovora.Pri poizvedbah za {type} zapise na "{query1}" in "{query2}", domenski strežnik {ns} odgovori z različnima RCODE ("{rcode1}" in "{rcode2}").Pri poizvedbah za {type} zapise na "{query1}" in "{query2}", domenski strežnik {ns} vrne različne odgovore.Pri poizvedbah za {type} zapise na "{query1}" in "{query2}", domenski strežnik {ns} vrne enak RCODE "{rcode}".Pri poizvedbah za {type} zapise na "{query1}" in "{query2}", domenski strežnik {ns} vrne enaka odgovora.Napačno ime lastnika ("{domain}") v SOA zapisu NODATA odgovora z NSEC. Podatki pridobljeni iz "{ns_list}".Napačno ime lastnika ("{domain}") v SOA zapisu NODATA odgovora z NSEC3. Podatki pridobljeni iz "{ns_list}".Cona ima NSEC ali NSEC3 zapise{child} je poslal DNSKEY zapis, toda {parent} ni poslal DS zapisa.{parent} je poslal DS zapis, {child} pa DNSKEY zapis.Starševska cona {parent} je poslala DS zapis, podrejena cona {child} pa ni poslala DNSKEY zapisa.