View on GitHub

DNSViz: A DNS visualization tool

git.rnl.tecnico.ulisboa.pt

Updated: 2024-11-10 22:31:28 UTC (518 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 (2)
  • git.rnl.tecnico.ulisboa.pt/CNAME
  • gitlab.rnl.tecnico.ulisboa.pt/A
Secure (2)
  • tecnico.ulisboa.pt/SOA
  • tecnico.ulisboa.pt/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • NSEC3 proving non-existence of rnl.tecnico.ulisboa.pt/DS
  • pt/DNSKEY (alg 13, id 30640)
  • pt/DNSKEY (alg 13, id 40155)
  • pt/DS (alg 13, id 40155)
  • tecnico.ulisboa.pt/DNSKEY (alg 13, id 29644)
  • tecnico.ulisboa.pt/DNSKEY (alg 13, id 9738)
  • tecnico.ulisboa.pt/DS (alg 13, id 9738)
  • ulisboa.pt/DNSKEY (alg 5, id 4368)
  • ulisboa.pt/DNSKEY (alg 5, id 502)
  • ulisboa.pt/DS (alg 5, id 502)

Delegation statusDelegation status

Insecure (1)
  • tecnico.ulisboa.pt to rnl.tecnico.ulisboa.pt
Secure (3)
  • . to pt
  • pt to ulisboa.pt
  • ulisboa.pt to tecnico.ulisboa.pt

NoticesNotices

Errors (4)
  • NSEC3 proving non-existence of rnl.tecnico.ulisboa.pt/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 rnl.tecnico.ulisboa.pt/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • tecnico.ulisboa.pt zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:690:21c0:a::150)
  • ulisboa.pt zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:690:21c0:a::150, 2001:690:21c0:b::150)
Warnings (8)
  • NSEC3 proving non-existence of rnl.tecnico.ulisboa.pt/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of rnl.tecnico.ulisboa.pt/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG tecnico.ulisboa.pt/DS alg 5, id 4368: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ulisboa.pt/DNSKEY alg 5, id 4368: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ulisboa.pt/DNSKEY alg 5, id 4368: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ulisboa.pt/DNSKEY alg 5, id 502: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ulisboa.pt/DNSKEY alg 5, id 502: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • pt to ulisboa.pt: The glue address(es) for ns2.tecnico.ulisboa.pt (2001:690:2100:1::2) differed from its authoritative address(es) (2001:690:2100:1::53:2). See RFC 1034, Sec. 4.2.2.

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