mbda.gov
Updated:
2023-10-18 15:37:16 UTC (184 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- mbda.gov/A
- mbda.gov/MX
- mbda.gov/NS
- mbda.gov/SOA
- mbda.gov/TXT
DNSKEY/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 status
Secure (2)
- . to gov
- gov to mbda.gov
Notices
Errors (3)
- mbda.gov zone: The server(s) were not responsive to queries over UDP. (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). (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). (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 (11)
- gov to mbda.gov: Authoritative AAAA records exist for gpaens2.doc.gov, but there are no corresponding AAAA glue records.
- gov to mbda.gov: Authoritative AAAA records exist for hchbens1.doc.gov, but there are no corresponding AAAA glue records.
- 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
- 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. (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. (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. (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. (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. (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. (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. (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. (2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
