dslbank.de

Updated: 2022-02-09 17:54:30 UTC (1055 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (3)

dslbank.de/MX
dslbank.de/NS
dslbank.de/SOA

DNSKEY/DS/NSEC status

Secure (10)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 9799)
de/DNSKEY (alg 8, id 26019)
de/DNSKEY (alg 8, id 26755)
de/DNSKEY (alg 8, id 58473)
de/DS (alg 8, id 26755)
dslbank.de/DS (alg 7, id 18906)
dslbank.de/DS (alg 7, id 1974)
dslbank.de/DS (alg 7, id 47088)
dslbank.de/DS (alg 7, id 52866)

Non_existent (6)

dslbank.de/DNSKEY (alg 7, id 11360)
dslbank.de/DNSKEY (alg 7, id 18788)
dslbank.de/DNSKEY (alg 7, id 18906)
dslbank.de/DNSKEY (alg 7, id 1974)
dslbank.de/DNSKEY (alg 7, id 47088)
dslbank.de/DNSKEY (alg 7, id 52866)

Delegation status

Bogus (1)

de to dslbank.de

Secure (1)

. to de

Notices

Errors (22)

de to dslbank.de: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
dslbank.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.157.35.19)
dslbank.de zone: There was an error resolving the following NS name(s) to address(es): ns1.postbank.de, ns2.postbank.de, ns3.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, 185.157.33.32, UDP_-_NOEDNS_)
dslbank.de/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, 185.157.33.32, TCP_-_EDNS0_4096_D_KN)
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, 185.157.33.32, UDP_-_EDNS0_512_D_KN)
dslbank.de/MX: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (185.157.33.19, UDP_-_NOEDNS_)
dslbank.de/MX: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (185.157.33.19, UDP_-_EDNS0_4096_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.32, 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, 185.157.33.32, UDP_-_EDNS0_512_D_KN)
dslbank.de/MX: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (185.157.33.19, UDP_-_EDNS0_4096_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.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, 185.157.33.32, UDP_-_NOEDNS_)
dslbank.de/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (185.157.33.32, UDP_-_EDNS0_4096_)
dslbank.de/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (185.157.33.32, UDP_-_EDNS0_4096_D_KN)
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, 185.157.33.32, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
dslbank.de/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (185.157.33.32, UDP_-_EDNS0_4096_D_KN)
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, 185.157.33.32, UDP_-_NOEDNS_)
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.
e2ldhckvyz.dslbank.de/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (17)

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: 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-09 17:53:39+00:00) is within possible clock skew range (51 seconds) of the current time (2022-02-09 17:54:30+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dslbank.de/NS alg 7, id 11360: The value of the Signature Inception field of the RRSIG RR (2022-02-09 17:53:44+00:00) is within possible clock skew range (46 seconds) of the current time (2022-02-09 17:54:30+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: 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-09 17:53:39+00:00) is within possible clock skew range (51 seconds) of the current time (2022-02-09 17:54:30+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dslbank.de/NS alg 7, id 18788: The value of the Signature Inception field of the RRSIG RR (2022-02-09 17:53:44+00:00) is within possible clock skew range (46 seconds) of the current time (2022-02-09 17:54:30+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 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 11360: The value of the Signature Inception field of the RRSIG RR (2022-02-09 17:50:46+00:00) is within possible clock skew range (3 minutes) of the current time (2022-02-09 17:54:30+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dslbank.de/SOA alg 7, id 11360: The value of the Signature Inception field of the RRSIG RR (2022-02-09 17:52:25+00:00) is within possible clock skew range (2 minutes) of the current time (2022-02-09 17:54:30+00:00). See RFC 4035, Sec. 5.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.
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.
RRSIG dslbank.de/SOA alg 7, id 18788: The value of the Signature Inception field of the RRSIG RR (2022-02-09 17:50:46+00:00) is within possible clock skew range (3 minutes) of the current time (2022-02-09 17:54:30+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dslbank.de/SOA alg 7, id 18788: The value of the Signature Inception field of the RRSIG RR (2022-02-09 17:52:25+00:00) is within possible clock skew range (2 minutes) of the current time (2022-02-09 17:54:30+00:00). See RFC 4035, Sec. 5.3.1.
dslbank.de/NS: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (185.157.33.32, UDP_-_EDNS0_4096_D_KN)