View on GitHub

DNSViz: A DNS visualization tool

integrity.gov

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

RRset statusRRset status

Bogus (6)
  • integrity.gov/A
  • integrity.gov/MX
  • integrity.gov/NS
  • integrity.gov/NSEC3PARAM
  • integrity.gov/SOA
  • integrity.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • integrity.gov/DNSKEY (alg 13, id 1691)
  • integrity.gov/DNSKEY (alg 13, id 64360)
Secure (7)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • integrity.gov/DS (alg 10, id 11913)
  • integrity.gov/DS (alg 10, id 7014)
Non_existent (2)
  • integrity.gov/DNSKEY (alg 10, id 11913)
  • integrity.gov/DNSKEY (alg 10, id 7014)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • gov to integrity.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. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to integrity.gov: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • integrity.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.134.208.70, 199.134.208.90)
  • integrity.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.134.208.70, 199.134.208.90, UDP_-_NOEDNS_)
  • integrity.gov/A: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
  • integrity.gov/DNSKEY (alg 13, id 1691): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • integrity.gov/DNSKEY (alg 13, id 64360): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • integrity.gov/MX: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • integrity.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.134.208.70, 199.134.208.90, UDP_-_NOEDNS_)
  • integrity.gov/NS: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
  • integrity.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
  • integrity.gov/SOA: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • integrity.gov/TXT: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.227.132, UDP_-_EDNS0_4096_D_KN)
  • integrity.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • integrity.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • oh07bxnu85.integrity.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • integrity.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • integrity.gov/DS (alg 10, id 7014): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • integrity.gov/DS (alg 10, id 7014): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • integrity.gov/DS (alg 10, id 7014): 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.
  • integrity.gov/DS (alg 10, id 7014): 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.
  • integrity.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • oh07bxnu85.integrity.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • integrity.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