mesh.gov
Updated:
2024-10-30 10:48:09 UTC (22 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (12)
- mesh.gov/A
- mesh.gov/AAAA
- mesh.gov/MX
- mesh.gov/NS
- mesh.gov/NSEC3PARAM
- mesh.gov/NSEC3PARAM
- mesh.gov/NSEC3PARAM
- mesh.gov/NSEC3PARAM
- mesh.gov/NSEC3PARAM
- mesh.gov/NSEC3PARAM
- mesh.gov/SOA
- mesh.gov/TXT
DNSKEY/DS/NSEC status
Bogus (2)
- mesh.gov/DNSKEY (alg 8, id 11565)
- mesh.gov/DNSKEY (alg 8, id 43789)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- gov/DNSKEY (alg 13, id 2536)
- gov/DNSKEY (alg 13, id 35496)
- gov/DS (alg 13, id 2536)
- mesh.gov/DS (alg 8, id 58792)
Non_existent (1)
- mesh.gov/DNSKEY (alg 8, id 58792)
Delegation status
Bogus (1)
- gov to mesh.gov
Secure (1)
- . to gov
Notices
Errors (8)
- gov to mesh.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. (130.14.252.50, 130.14.252.53, 165.112.6.3, 2607:f220:41e:252::50, 2607:f220:41e:252::53, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_KN)
- gov to mesh.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (130.14.252.50, 130.14.252.53, 165.112.6.3, 2607:f220:41e:252::50, 2607:f220:41e:252::53, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 2607:f220:41e:252::50, 2607:f220:41e:252::53, UDP_-_EDNS0_512_D_KN)
- mesh.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- mesh.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- mesh.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- alnjy.twf5g.mesh.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- mesh.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- mesh.gov/DNSKEY (alg 8, id 11565): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (130.14.252.50, 130.14.252.53, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/DNSKEY (alg 8, id 43789): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (130.14.252.50, 130.14.252.53, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (130.14.252.50, 130.14.252.53, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- mesh.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. (130.14.252.53, UDP_-_EDNS0_4096_D_KN_0x20)
- mesh.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- mesh.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- mesh.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- alnjy.twf5g.mesh.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- mesh.gov/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
