View on GitHub

DNSViz: A DNS visualization tool

internet4all.gov

Updated: 2023-02-07 22:03:35 UTC (586 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

Secure (4)
  • internet4all.gov/A
  • internet4all.gov/NS
  • internet4all.gov/SOA
  • internet4all.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • internet4all.gov/DNSKEY (alg 5, id 11121)
  • internet4all.gov/DNSKEY (alg 5, id 30373)
  • internet4all.gov/DS (alg 5, id 30373)
  • internet4all.gov/DS (alg 5, id 30373)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to internet4all.gov

NoticesNotices

Warnings (18)
  • RRSIG internet4all.gov/A alg 5, id 11121: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/DNSKEY alg 5, id 11121: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/DNSKEY alg 5, id 11121: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/DNSKEY alg 5, id 30373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/DNSKEY alg 5, id 30373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/NS alg 5, id 11121: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/SOA alg 5, id 11121: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG internet4all.gov/TXT alg 5, id 11121: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • internet4all.gov/DS (alg 5, id 30373): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • internet4all.gov/DS (alg 5, id 30373): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • internet4all.gov/DS (alg 5, id 30373): 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.
  • internet4all.gov/DS (alg 5, id 30373): 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.
  • internet4all.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • internet4all.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 6r04evy8fo.internet4all.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • internet4all.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • internet4all.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • internet4all.gov/NSEC3PARAM 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