udl.cat
Updated:
2023-10-31 13:03:24 UTC (442 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- udl.cat/A
- udl.cat/MX
- udl.cat/NS
- udl.cat/SOA
- udl.cat/TXT
Secure (2)
- cat/SOA
- cat/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of udl.cat/DS
- cat/DNSKEY (alg 10, id 45116)
- cat/DNSKEY (alg 10, id 58737)
- cat/DS (alg 10, id 58737)
Delegation status
Insecure (1)
- cat to udl.cat
Secure (1)
- . to cat
Notices
Errors (1)
- cat zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (84.88.0.162, 2001:40b0:1:3::2)
Warnings (7)
- RRSIG NSEC3 proving non-existence of udl.cat/DS alg 10, id 45116: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG cat/SOA alg 10, id 45116: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG cat/SOA alg 10, id 45116: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- cat to udl.cat: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the cat zone): chico.rediris.es, sun.rediris.es See RFC 1034, Sec. 4.2.2.
- udl.cat/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
