View on GitHub

DNSViz: A DNS visualization tool

mbda.gov

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

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • mbda.gov/DS (alg 8, id 63907)
Non_existent (1)
  • mbda.gov/DNSKEY (alg 8, id 63907)

Delegation statusDelegation status

Bogus (1)
  • gov to mbda.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (28)
  • gov to mbda.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
  • mbda.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (64.62.200.147, 108.166.170.104, 170.110.225.11, 170.110.225.13, 170.110.225.16, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225)
  • mbda.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (64.62.200.147, 108.166.170.104, 170.110.225.11, 170.110.225.13, 170.110.225.16, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225)
  • mbda.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238)
  • mbda.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238, UDP_-_NOEDNS_)
  • mbda.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (64.62.200.147, 108.166.170.104, 170.110.225.11, 170.110.225.13, 170.110.225.16, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
  • mbda.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (64.62.200.147, 108.166.170.104, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_NOEDNS_)
  • mbda.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
  • mbda.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (64.62.200.147, UDP_-_NOEDNS_)
  • mbda.gov/DNSKEY: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (108.166.170.104, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_NOEDNS_)
  • mbda.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (64.62.200.147, 108.166.170.104, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_EDNS0_512_D_K)
  • mbda.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • mbda.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (64.62.200.147, 198.255.114.190, 2001:470:1:7a::147, UDP_-_NOEDNS_)
  • mbda.gov/MX: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (108.166.170.104, 192.198.87.242, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_NOEDNS_)
  • mbda.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (108.166.170.104, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_EDNS0_512_D_K)
  • mbda.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (64.62.200.147, 170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • mbda.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238, UDP_-_NOEDNS_)
  • mbda.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (64.62.200.147, 108.166.170.104, 170.110.225.11, 170.110.225.13, 170.110.225.16, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
  • mbda.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (64.62.200.147, 108.166.170.104, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • mbda.gov/SOA: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (198.255.114.190, 2001:470:1:7a::147, UDP_-_NOEDNS_)
  • mbda.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • mbda.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (64.62.200.147, 108.166.170.104, 170.110.225.11, 170.110.225.13, 170.110.225.16, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, TCP_-_NOEDNS_)
  • mbda.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (64.62.200.147, UDP_-_NOEDNS_)
  • mbda.gov/TXT: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (108.166.170.104, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2607:5600:143:0:1000::101, 2607:f348:100c:1::171, UDP_-_NOEDNS_)
  • mbda.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
  • mbda.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • mbda.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 91ulmptj2s.mbda.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • gov to mbda.gov: Authoritative AAAA records exist for gpaens2.doc.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to mbda.gov: Authoritative AAAA records exist for hchbens1.doc.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.
  • mbda.gov/DS (alg 8, id 63907): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mbda.gov/DS (alg 8, id 63907): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mbda.gov/DS (alg 8, id 63907): 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.
  • mbda.gov/DS (alg 8, id 63907): 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.

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