View on GitHub

DNSViz: A DNS visualization tool

uminho.pt

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (4)
  • uminho.pt/MX
  • uminho.pt/NS
  • uminho.pt/SOA
  • uminho.pt/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • pt/DNSKEY (alg 7, id 21299)
  • pt/DNSKEY (alg 7, id 40995)
  • pt/DS (alg 7, id 40995)
  • pt/DS (alg 7, id 40995)
  • uminho.pt/DNSKEY (alg 5, id 36028)
  • uminho.pt/DNSKEY (alg 5, id 51330)
  • uminho.pt/DS (alg 5, id 36028)
  • uminho.pt/DS (alg 5, id 36028)

Delegation statusDelegation status

Secure (2)
  • . to pt
  • pt to uminho.pt

NoticesNotices

Warnings (30)
  • RRSIG pt/DNSKEY alg 7, id 40995: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pt/DNSKEY alg 7, id 40995: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/DNSKEY alg 5, id 36028: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/DNSKEY alg 5, id 36028: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/DNSKEY alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/DNSKEY alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/DS alg 7, id 21299: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/DS alg 7, id 21299: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/MX alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/NS alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/SOA alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uminho.pt/TXT alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • pt/DS (alg 7, id 40995): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • pt/DS (alg 7, id 40995): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • pt/DS (alg 7, id 40995): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • pt/DS (alg 7, id 40995): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • uminho.pt/DS (alg 5, id 36028): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uminho.pt/DS (alg 5, id 36028): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uminho.pt/DS (alg 5, id 36028): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • uminho.pt/DS (alg 5, id 36028): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • uminho.pt/DS (alg 5, id 36028): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (185.39.210.1, UDP_-_EDNS0_4096_D_K)
  • uminho.pt/DS (alg 5, id 36028): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (185.39.210.1, UDP_-_EDNS0_4096_D_K)
  • uminho.pt/DS (alg 5, id 36028): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (185.39.210.1, UDP_-_EDNS0_4096_D_K)
  • uminho.pt/DS (alg 5, id 36028): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (185.39.210.1, UDP_-_EDNS0_4096_D_K)
  • uminho.pt/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uminho.pt/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uminho.pt/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uminho.pt/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • g0xolkzhjd.uminho.pt/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uminho.pt/DNSKEY 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