View on GitHub

DNSViz: A DNS visualization tool

faasafety.gov

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

RRset statusRRset status

Secure (6)
  • faasafety.gov/A
  • faasafety.gov/MX
  • faasafety.gov/NS
  • faasafety.gov/NSEC3PARAM
  • faasafety.gov/SOA
  • faasafety.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • faasafety.gov/DNSKEY (alg 10, id 20645)
  • faasafety.gov/DNSKEY (alg 10, id 49247)
  • faasafety.gov/DNSKEY (alg 13, id 19519)
  • faasafety.gov/DS (alg 13, id 19519)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to faasafety.gov

NoticesNotices

Errors (16)
  • faasafety.gov/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/A: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/MX: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/NS: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • faasafety.gov/SOA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • faasafety.gov/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • faasafety.gov/TXT: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
  • gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:74:27::2:30, 2620:74:29::2:30)
  • faasafety.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • faasafety.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • eyugpoqv25.faasafety.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • RRSIG faasafety.gov/A alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/DNSKEY alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/DNSKEY alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/DNSKEY alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/MX alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/NS alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/NSEC3PARAM alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/SOA alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faasafety.gov/TXT alg 10, id 20645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • faasafety.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • faasafety.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • faasafety.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eyugpoqv25.faasafety.gov/A 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