NSEC3 proving non-existence of dslbank.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dslbank.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dslbank.de zone: The following NS name(s) did not resolve to address(es): ns1.postbank.de, ns3.postbank.de
dslbank.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.157.33.32, 185.157.35.19)
dslbank.de zone: There was an error resolving the following NS name(s) to address(es): ns2.postbank.de
dslbank.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, 185.157.33.32, 185.157.35.19, UDP_-_NOEDNS_)
dslbank.de/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
dslbank.de/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
dslbank.de/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_EDNS0_512_D_KN)
dslbank.de/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
dslbank.de/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_EDNS0_512_D_KN)
dslbank.de/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.32, 185.157.35.19, UDP_-_NOEDNS_)
dslbank.de/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
dslbank.de/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
dslbank.de/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
48lvad92y7.dslbank.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
dslbank.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
dslbank.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
dslbank.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
NSEC3 proving non-existence of dslbank.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dslbank.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
RRSIG dslbank.de/NS alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG dslbank.de/NS alg 7, id 11360: The value of the Signature Inception field of the RRSIG RR (2022-02-11 17:45:58+00:00) is within possible clock skew range (4 minutes) of the current time (2022-02-11 17:50:37+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dslbank.de/NS alg 7, id 18788: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG dslbank.de/NS alg 7, id 18788: The value of the Signature Inception field of the RRSIG RR (2022-02-11 17:45:58+00:00) is within possible clock skew range (4 minutes) of the current time (2022-02-11 17:50:37+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dslbank.de/SOA alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG dslbank.de/SOA alg 7, id 18788: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
dslbank.de/DS has warnings; select the "Denial of existence" DNSSEC option to see them.