View on GitHub

DNSViz: A DNS visualization tool

hq.dhs.gov

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

RRset statusRRset status

Bogus (2)
  • hq.dhs.gov/MX
  • hq.dhs.gov/SOA
Secure (4)
  • hq.dhs.gov/MX (NODATA)
  • hq.dhs.gov/NS
  • hq.dhs.gov/SOA
  • hq.dhs.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • NSEC proving non-existence of hq.dhs.gov/MX
  • dhs.gov/DNSKEY (alg 8, id 19269)
  • dhs.gov/DNSKEY (alg 8, id 4969)
  • dhs.gov/DNSKEY (alg 8, id 7435)
  • dhs.gov/DS (alg 8, id 43330)
  • dhs.gov/DS (alg 8, id 7435)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DS (alg 8, id 64280)
  • hq.dhs.gov/DNSKEY (alg 13, id 2371)
  • hq.dhs.gov/DNSKEY (alg 13, id 34505)
  • hq.dhs.gov/DS (alg 13, id 2371)
Non_existent (1)
  • dhs.gov/DNSKEY (alg 8, id 43330)

Delegation statusDelegation status

Secure (3)
  • . to gov
  • dhs.gov to hq.dhs.gov
  • gov to dhs.gov

NoticesNotices

Errors (17)
  • NSEC proving non-existence of hq.dhs.gov/MX: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: hq.dhs.gov/MX See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of hq.dhs.gov/MX: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: hq.dhs.gov/MX See RFC 4035, Sec. 3.1.3.1.
  • dhs.gov to hq.dhs.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. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dhs.gov to hq.dhs.gov: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • dhs.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (193.108.91.91, 2600:1406:32::40, 2a02:26f0:117::42)
  • hq.dhs.gov/DNSKEY (alg 13, id 2371): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • hq.dhs.gov/DNSKEY (alg 13, id 34505): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • hq.dhs.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • hq.dhs.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN)
  • hq.dhs.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • hq.dhs.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1480:7800::42, UDP_-_EDNS0_4096_D_KN)
  • hq.dhs.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • hq.dhs.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • hq.dhs.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • hq.dhs.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • a2fby957lt.hq.dhs.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • hq.dhs.gov/A has errors; 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