View on GitHub

DNSViz: A DNS visualization tool

safetyact.gov

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

RRset statusRRset status

Bogus (4)
  • safetyact.gov/A
  • safetyact.gov/NS
  • safetyact.gov/SOA
  • safetyact.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 36558)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • safetyact.gov/DS (alg 8, id 17842)
Non_existent (1)
  • safetyact.gov/DNSKEY (alg 8, id 17842)

Delegation statusDelegation status

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

NoticesNotices

Errors (12)
  • gov to safetyact.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, 193.108.91.91, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1406:32::40, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • gov to safetyact.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. (2.16.40.65, 23.61.199.64, 23.211.61.66, 23.211.132.67, 184.85.248.66, 193.108.91.91, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1406:32::40, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • safetyact.gov zone: The following NS name(s) did not resolve to address(es): f5-gtm-external3.dc1.dhs.gov
  • safetyact.gov/A: 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, 193.108.91.91, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1406:32::40, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_K)
  • safetyact.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, 193.108.91.91, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1406:32::40, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_K)
  • safetyact.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, 193.108.91.91, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1406:32::40, 2a02:26f0:117::42, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • safetyact.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, 193.108.91.91, 2600:1401:2::5b, 2600:1403:a::41, 2600:1406:1b::43, 2600:1406:32::40, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_K)
  • safetyact.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 06cz5salfh.safetyact.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • gov to safetyact.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): f5-gtm-external3.dc1.dhs.gov See RFC 1034, Sec. 4.2.2.
  • gov to safetyact.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: a1-91.akam.net, a16-67.akam.net, a22-66.akam.net, a7-64.akam.net, a8-65.akam.net, a9-66.akam.net See RFC 1034, Sec. 4.2.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): 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.

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