View on GitHub

DNSViz: A DNS visualization tool

ameslab.gov

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

RRset statusRRset status

Secure (5)
  • ameslab.gov/MX
  • ameslab.gov/NS
  • ameslab.gov/SOA
  • ameslab.gov/SOA
  • ameslab.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • ameslab.gov/DNSKEY (alg 8, id 39541)
  • ameslab.gov/DNSKEY (alg 8, id 41791)
  • ameslab.gov/DNSKEY (alg 8, id 64185)
  • ameslab.gov/DS (alg 8, id 39541)
  • ameslab.gov/DS (alg 8, id 39541)
  • ameslab.gov/DS (alg 8, id 41791)
  • ameslab.gov/DS (alg 8, id 41791)
  • 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 ameslab.gov

NoticesNotices

Errors (15)
  • ameslab.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2)
  • ameslab.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2)
  • ameslab.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (147.155.1.1, 2620:57:0:2c6::1)
  • ameslab.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • ameslab.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • ameslab.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (147.155.1.1, 2620:57:0:2c6::1, UDP_-_NOEDNS_)
  • ameslab.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2, UDP_-_NOEDNS_)
  • ameslab.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2, TCP_-_NOEDNS_)
  • ameslab.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • ameslab.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (129.186.67.145, 2610:130:102:112::2, UDP_-_NOEDNS_)
  • ameslab.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ameslab.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • az93txnq2u.ameslab.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ameslab.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ameslab.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
  • ameslab.gov/DS (alg 8, id 39541): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ameslab.gov/DS (alg 8, id 39541): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ameslab.gov/DS (alg 8, id 39541): 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.
  • ameslab.gov/DS (alg 8, id 39541): 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.
  • ameslab.gov/DS (alg 8, id 41791): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ameslab.gov/DS (alg 8, id 41791): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ameslab.gov/DS (alg 8, id 41791): 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.
  • ameslab.gov/DS (alg 8, id 41791): 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 to ameslab.gov: Authoritative AAAA records exist for fiber.ameslab.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to ameslab.gov: Authoritative AAAA records exist for scsds.ameslab.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.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): 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.
  • ameslab.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • az93txnq2u.ameslab.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ameslab.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ameslab.gov/AAAA 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