View on GitHub

DNSViz: A DNS visualization tool

cancer.gov

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

RRset statusRRset status

Secure (6)
  • cancer.gov/A
  • cancer.gov/AAAA
  • cancer.gov/MX
  • cancer.gov/NS
  • cancer.gov/SOA
  • cancer.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • cancer.gov/DNSKEY (alg 7, id 18960)
  • cancer.gov/DNSKEY (alg 7, id 32975)
  • cancer.gov/DNSKEY (alg 7, id 33678)
  • cancer.gov/DNSKEY (alg 7, id 45749)
  • cancer.gov/DS (alg 7, id 18960)
  • cancer.gov/DS (alg 7, id 18960)
  • cancer.gov/DS (alg 7, id 33678)
  • cancer.gov/DS (alg 7, id 33678)
  • gov/DNSKEY (alg 8, id 40176)
  • 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 cancer.gov

NoticesNotices

Errors (7)
  • cancer.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (165.112.4.230)
  • cancer.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401)
  • cancer.gov/A: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_NOEDNS_)
  • cancer.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_NOEDNS_)
  • cancer.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (165.112.4.230, TCP_-_EDNS0_4096_D)
  • cancer.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3f8d6uq29t.cancer.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (47)
  • RRSIG cancer.gov/A alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/A alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/AAAA alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/AAAA alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 18960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 18960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 18960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 18960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 33678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 33678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 33678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 33678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/DNSKEY alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/MX alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/MX alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/NS alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/NS alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/SOA alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/SOA alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/TXT alg 7, id 32975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cancer.gov/TXT alg 7, id 45749: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • cancer.gov/DNSKEY (alg 7, id 18960): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
  • cancer.gov/DNSKEY (alg 7, id 32975): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
  • cancer.gov/DNSKEY (alg 7, id 33678): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
  • cancer.gov/DNSKEY (alg 7, id 45749): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
  • cancer.gov/DS (alg 7, id 18960): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cancer.gov/DS (alg 7, id 18960): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cancer.gov/DS (alg 7, id 18960): 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.
  • cancer.gov/DS (alg 7, id 18960): 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.
  • cancer.gov/DS (alg 7, id 33678): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cancer.gov/DS (alg 7, id 33678): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cancer.gov/DS (alg 7, id 33678): 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.
  • cancer.gov/DS (alg 7, id 33678): 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): 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.
  • cancer.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cancer.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 3f8d6uq29t.cancer.gov/A 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