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 (8)
  • safetyact.gov/A
  • safetyact.gov/NS
  • safetyact.gov/NSEC3PARAM
  • safetyact.gov/NSEC3PARAM
  • safetyact.gov/NSEC3PARAM
  • safetyact.gov/NSEC3PARAM
  • safetyact.gov/SOA
  • safetyact.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (3)
  • safetyact.gov/DNSKEY (alg 10, id 49517)
  • safetyact.gov/DNSKEY (alg 10, id 60054)
  • safetyact.gov/DNSKEY (alg 10, id 62927)
Secure (8)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 56278)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • safetyact.gov/DS (alg 10, id 30393)
Non_existent (1)
  • safetyact.gov/DNSKEY (alg 10, id 30393)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • 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. (173.255.59.114, 173.255.59.115, 216.81.89.101, 216.81.89.102, UDP_-_EDNS0_4096_D_KN)
  • gov to safetyact.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. (173.255.59.114, 173.255.59.115, 216.81.89.101, 216.81.89.102, UDP_-_EDNS0_4096_D_KN)
  • safetyact.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (216.81.81.101, 216.81.81.102)
  • safetyact.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (216.81.81.101, 216.81.81.102, UDP_-_NOEDNS_)
  • safetyact.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (216.81.81.101, 216.81.81.102, UDP_-_NOEDNS_)
  • 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.
  • 1obsfzc2gy.safetyact.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (80)
  • RRSIG safetyact.gov/A alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/A alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 60054: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/DNSKEY alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NS alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/NSEC3PARAM alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/SOA alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 49517: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG safetyact.gov/TXT alg 10, id 62927: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • 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): dcap1-f5-gtm-external2.dcap1.dhs.gov, dcap1-f5-gtm-external1.dcap1.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: f5-gtm-external1.dc2.dhs.gov, f5-gtm-external2.dc2.dhs.gov See RFC 1034, Sec. 4.2.2.
  • safetyact.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 1obsfzc2gy.safetyact.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • safetyact.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