View on GitHub

DNSViz: A DNS visualization tool

safgrandchallenge.gov

« 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 (6)
  • gov/SOA
  • gov/SOA
  • safgrandchallenge.gov/A (NODATA)
  • safgrandchallenge.gov/A (NXDOMAIN)
  • safgrandchallenge.gov/AAAA (NODATA)
  • safgrandchallenge.gov/AAAA (NXDOMAIN)

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC proving non-existence of safgrandchallenge.gov/A
  • NSEC proving non-existence of safgrandchallenge.gov/AAAA
  • NSEC3 proving non-existence of safgrandchallenge.gov/A
  • NSEC3 proving non-existence of safgrandchallenge.gov/AAAA
  • 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)

Delegation statusDelegation status

Secure (1)
  • . to gov

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of safgrandchallenge.gov/A: 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 safgrandchallenge.gov/A: 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 safgrandchallenge.gov/AAAA: 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 safgrandchallenge.gov/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • NSEC3 proving non-existence of safgrandchallenge.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of safgrandchallenge.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of safgrandchallenge.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of safgrandchallenge.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • gov/DNSKEY (alg 8, id 40921): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (69.36.153.30, 69.36.157.30, 81.19.194.30, 209.112.123.30, 2001:500:4431::2:30, 2620:74:27::2:30, 2620:74:28::2:30, 2620:74:29::2:30, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • gov/CNAME 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