mesh.gov
Updated:
2022-12-12 14:30:59 UTC (710 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- mesh.gov/MX (NODATA)
- mesh.gov/NS (NODATA)
- mesh.gov/NSEC3PARAM
- mesh.gov/SOA (NODATA)
- mesh.gov/TXT (NODATA)
Secure (11)
- 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/SOA
- mesh.gov/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- mesh.gov/DNSKEY (alg 8, id 42033)
- mesh.gov/DNSKEY (alg 8, id 5749)
- mesh.gov/DS (alg 8, id 5749)
Delegation status
Secure (2)
- . to gov
- gov to mesh.gov
Notices
Errors (19)
- mesh.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 165.112.6.3)
- mesh.gov/DNSKEY: No response was received from the server over UDP (tried 10 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::53, UDP_-_EDNS0_4096_D_N)
- 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, UDP_-_EDNS0_512_D_KN)
- mesh.gov/MX (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- mesh.gov/MX (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- mesh.gov/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/NS (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/NSEC3PARAM: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (130.14.252.50, UDP_-_EDNS0_4096_)
- mesh.gov/NSEC3PARAM: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (130.14.252.50, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/NSEC3PARAM: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (130.14.252.50, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- mesh.gov/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- mesh.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 165.112.6.3, TCP_-_EDNS0_4096_D_N)
- mesh.gov/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::53, TCP_-_EDNS0_4096_D_0x20)
- mesh.gov/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/TXT (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_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.
- yl9cno7zt8.mesh.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- mesh.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. (130.14.252.50, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/NSEC3PARAM: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (130.14.252.53, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2607:f220:41e:252::50, 2607:f220:41e:252::53, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/TXT: 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. (2607:f220:41e:252::53, UDP_-_EDNS0_4096_D_KN)
- mesh.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- yl9cno7zt8.mesh.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
