View on GitHub

DNSViz: A DNS visualization tool

urv.cat

Updated: 2021-03-06 12:54:00 UTC (1410 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • urv.cat/A
  • urv.cat/MX
  • urv.cat/NS
  • urv.cat/SOA
  • urv.cat/TXT
Secure (1)
  • cat/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of urv.cat/DS
  • cat/DNSKEY (alg 10, id 4863)
  • cat/DNSKEY (alg 10, id 4872)
  • cat/DNSKEY (alg 10, id 58737)
  • cat/DS (alg 10, id 58737)

Delegation statusDelegation status

Insecure (1)
  • cat to urv.cat
Secure (1)
  • . to cat

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of urv.cat/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 urv.cat/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • urv.cat/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • NSEC3 proving non-existence of urv.cat/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of urv.cat/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of urv.cat/DS alg 10, id 4863: 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/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 4863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • cat to urv.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): aliga.urv.cat, dns.urv.cat See RFC 1034, Sec. 4.2.2.
  • cat to urv.cat: The following NS name(s) were found in the delegation NS RRset (i.e., in the cat zone), but not in the authoritative NS RRset: aliga.urv.es, dns.urv.es, dns4.urv.es See RFC 1034, Sec. 4.2.2.
  • urv.cat/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph