postbank.de

Updated: 2022-02-10 06:32:12 UTC (1051 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 (2)

postbank.de/NS
postbank.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)
postbank.de/DS (alg 7, id 29904)
postbank.de/DS (alg 7, id 30588)
postbank.de/DS (alg 7, id 37863)
postbank.de/DS (alg 7, id 46596)

Non_existent (6)

postbank.de/DNSKEY (alg 7, id 12287)
postbank.de/DNSKEY (alg 7, id 29904)
postbank.de/DNSKEY (alg 7, id 30588)
postbank.de/DNSKEY (alg 7, id 37863)
postbank.de/DNSKEY (alg 7, id 46596)
postbank.de/DNSKEY (alg 7, id 63119)

Delegation status

Bogus (1)

de to postbank.de

Secure (1)

. to de

Notices

Errors (17)

de to postbank.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.
postbank.de zone: The following NS name(s) did not resolve to address(es): ns3.postbank.de
postbank.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)
postbank.de zone: There was an error resolving the following NS name(s) to address(es): ns1.postbank.de, ns2.postbank.de
postbank.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_)
postbank.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_)
postbank.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_)
postbank.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)
postbank.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_)
postbank.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)
postbank.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_)
postbank.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_)
postbank.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)
postbank.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_)
postbank.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
zrqew3mucn.postbank.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
postbank.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (4)

RRSIG postbank.de/NS alg 7, id 12287: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG postbank.de/NS alg 7, id 63119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG postbank.de/SOA alg 7, id 12287: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG postbank.de/SOA alg 7, id 63119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.