View on GitHub

DNSViz: A DNS visualization tool

mbda.gov

Updated: 2023-10-18 15:37:16 UTC (280 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 (5)
  • mbda.gov/A
  • mbda.gov/MX
  • mbda.gov/NS
  • mbda.gov/SOA
  • mbda.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 49735)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 64280)
  • gov/DS (alg 8, id 7698)
  • mbda.gov/DNSKEY (alg 8, id 30564)
  • mbda.gov/DNSKEY (alg 8, id 46188)
  • mbda.gov/DNSKEY (alg 8, id 52972)
  • mbda.gov/DS (alg 8, id 52972)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • mbda.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::237, 2001:49f0:d064:6:1000::238, 2607:5600:143:0:1000::101, 2607:5600:143:0:1000::245)
  • 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::237, 2001:49f0:d064:6:1000::238, 2607:5600:143:0:1000::101, 2607:5600:143:0:1000::245, 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::237, 2001:49f0:d064:6:1000::238, 2607:5600:143:0:1000::101, 2607:5600:143:0:1000::245, UDP_-_NOEDNS_)
Warnings (12)
  • 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 to mbda.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: hchbens2.doc.gov See RFC 1034, Sec. 4.2.2.
  • mbda.gov/A: 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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/DNSKEY (alg 8, id 30564): 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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/DNSKEY (alg 8, id 46188): 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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/DNSKEY (alg 8, id 52972): 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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/MX: 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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/NS: 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. (2610:20:0:20:d0c:90c:225:223, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/SOA: 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. (2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • mbda.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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
  • mbda.gov/DNSKEY 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