View on GitHub

DNSViz: A DNS visualization tool

iad.gov

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

RRset statusRRset status

Bogus (10)
  • iad.gov/A
  • iad.gov/A (NODATA)
  • iad.gov/MX
  • iad.gov/MX (NODATA)
  • iad.gov/NS
  • iad.gov/NS (NODATA)
  • iad.gov/SOA
  • iad.gov/SOA (NODATA)
  • iad.gov/TXT
  • iad.gov/TXT (NODATA)

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • iad.gov/DNSKEY (alg 8, id 36055)
  • iad.gov/DNSKEY (alg 8, id 41199)
  • iad.gov/DNSKEY (alg 8, id 61415)
  • iad.gov/DNSKEY (alg 8, id 6620)
Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 36558)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • iad.gov/DS (alg 8, id 61415)
  • iad.gov/DS (alg 8, id 61415)
  • iad.gov/DS (alg 8, id 6620)
  • iad.gov/DS (alg 8, id 6620)

Delegation statusDelegation status

Bogus (1)
  • gov to iad.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (33)
  • RRSIG iad.gov/A alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-03 19:56:52+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 6620: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 6620: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 6620: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/DNSKEY alg 8, id 6620: The Signature Expiration field of the RRSIG RR (2020-04-05 00:45:28+00:00) is 3 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/MX alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-03 19:56:52+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/NS alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-03 19:56:52+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/SOA alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-08 00:45:28+00:00) is 23 hours, 28 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG iad.gov/TXT alg 8, id 41199: The Signature Expiration field of the RRSIG RR (2020-04-03 19:56:52+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • gov to iad.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. (8.44.96.33, 8.44.96.34, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • gov to iad.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. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.gov zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (8.44.96.33)
  • iad.gov/A (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. (8.44.96.33, UDP_-_EDNS0_4096_D_K)
  • iad.gov/A (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (8.44.96.33, UDP_-_EDNS0_4096_D_K)
  • iad.gov/DNSKEY (alg 8, id 41199): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.gov/DNSKEY (alg 8, id 61415): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.gov/DNSKEY (alg 8, id 6620): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.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. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.gov/MX (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.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. (8.44.96.33, UDP_-_EDNS0_4096_D_K)
  • iad.gov/NS (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (8.44.96.33, UDP_-_EDNS0_4096_D_K)
  • iad.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. (8.44.96.33, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • iad.gov/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (8.44.96.33, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • iad.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. (8.44.96.33, UDP_-_EDNS0_4096_D_K)
  • iad.gov/TXT (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (8.44.96.33, UDP_-_EDNS0_4096_D_K)
  • otia2mhbsr.iad.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • iad.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • iad.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • iad.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • gov/DS (alg 8, id 7698): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • iad.gov/DNSKEY (alg 8, id 36055): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (8.44.96.33, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • iad.gov/DS (alg 8, id 61415): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • iad.gov/DS (alg 8, id 61415): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • iad.gov/DS (alg 8, id 61415): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • iad.gov/DS (alg 8, id 61415): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • iad.gov/DS (alg 8, id 6620): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • iad.gov/DS (alg 8, id 6620): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • iad.gov/DS (alg 8, id 6620): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • iad.gov/DS (alg 8, id 6620): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • otia2mhbsr.iad.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • iad.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • iad.gov/AAAA 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