View on GitHub

DNSViz: A DNS visualization tool

faa.gov

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

RRset statusRRset status

Secure (5)
  • faa.gov/MX
  • faa.gov/NS
  • faa.gov/NSEC3PARAM
  • faa.gov/SOA
  • faa.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • faa.gov/DNSKEY (alg 10, id 16040)
  • faa.gov/DNSKEY (alg 10, id 49653)
  • faa.gov/DNSKEY (alg 10, id 50372)
  • faa.gov/DNSKEY (alg 10, id 61700)
  • faa.gov/DS (alg 10, id 49653)
  • faa.gov/DS (alg 10, id 49653)
  • 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 faa.gov

NoticesNotices

Errors (7)
  • faa.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80)
  • faa.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_NOEDNS_)
  • 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)
  • faa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • faa.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • faa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gmkr0lj5nq.faa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
  • RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/DNSKEY alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/MX alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/NS alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/NSEC3PARAM alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/SOA alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG faa.gov/TXT alg 10, id 61700: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • faa.gov/DS (alg 10, id 49653): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • faa.gov/DS (alg 10, id 49653): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • faa.gov/DS (alg 10, id 49653): 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.
  • faa.gov/DS (alg 10, id 49653): 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.
  • faa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • faa.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • faa.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • faa.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gmkr0lj5nq.faa.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