View on GitHub

DNSViz: A DNS visualization tool

mesh.gov

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

RRset statusRRset status

Bogus (4)
  • mesh.gov/MX (NODATA)
  • mesh.gov/NS (NODATA)
  • 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 statusDNSKEY/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 statusDelegation status

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

NoticesNotices

Errors (25)
  • 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, 2607:f220:41f:1405::3)
  • mesh.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, UDP_-_NOEDNS_)
  • mesh.gov/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_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. (2607:f220:41e:252::50, 2607:f220:41f:1405::3, 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, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/MX (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/MX (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/MX: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_KN)
  • mesh.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, 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, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/NS (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/NS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/NS: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_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, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • mesh.gov/SOA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • mesh.gov/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, 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, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_N)
  • mesh.gov/SOA: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_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, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/TXT (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/TXT: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_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.
  • hrlaj6cv97.mesh.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • mesh.gov/A: 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::50, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/AAAA: 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, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/AAAA: 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. (2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
  • mesh.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. (2607:f220:41e:252::53, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/MX: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_512_D_KN)
  • 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. (2607:f220:41e:252::50, UDP_-_EDNS0_4096_D_KN)
  • mesh.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hrlaj6cv97.mesh.gov/A 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