View on GitHub

DNSViz: A DNS visualization tool

osde.gov

Updated: 2022-04-13 22:28:32 UTC (952 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 (2)
  • gov/SOA
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • NSEC3 proving non-existence of osde.gov/DS
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Lame (1)
  • gov to osde.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of osde.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of osde.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • osde.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154)
  • osde.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154)
  • osde.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_NOEDNS_)
  • osde.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_NOEDNS_)
  • osde.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • osde.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • osde.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_NOEDNS_)
  • osde.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_NOEDNS_)
  • osde.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, TCP_-_NOEDNS_)
  • osde.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • osde.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.115, 198.6.1.154, UDP_-_NOEDNS_)
  • 8xjmw30pbn.osde.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • osde.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • osde.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • osde.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of osde.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of osde.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • osde.gov/DS 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