View on GitHub

DNSViz: A DNS visualization tool

data.gov

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

RRset statusRRset status

Secure (5)
  • data.gov/A
  • data.gov/NS
  • data.gov/SOA
  • data.gov/SOA
  • data.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • data.gov/DNSKEY (alg 8, id 14866)
  • data.gov/DNSKEY (alg 8, id 54239)
  • data.gov/DNSKEY (alg 8, id 58579)
  • data.gov/DS (alg 8, id 54239)
  • data.gov/DS (alg 8, id 54239)
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • data.gov/DNSKEY (alg 8, id 14866): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (2600:1f16:8f2:d500:1::, UDP_-_EDNS0_4096_D_K)
  • data.gov/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (159.142.150.68, TCP_-_EDNS0_4096_D)
  • jry2cm1okh.data.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • data.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • data.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • data.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • data.gov/DS (alg 8, id 54239): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • data.gov/DS (alg 8, id 54239): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • data.gov/DS (alg 8, id 54239): 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.
  • data.gov/DS (alg 8, id 54239): 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.
  • data.gov/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (159.142.150.68, UDP_-_EDNS0_4096_D_K)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • jry2cm1okh.data.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • data.gov/MX 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