View on GitHub

DNSViz: A DNS visualization tool

fcc.gov

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

RRset statusRRset status

Secure (17)
  • fcc.gov/A
  • fcc.gov/A
  • fcc.gov/A
  • fcc.gov/A
  • fcc.gov/A
  • fcc.gov/A
  • fcc.gov/AAAA
  • fcc.gov/AAAA
  • fcc.gov/AAAA
  • fcc.gov/AAAA
  • fcc.gov/AAAA
  • fcc.gov/AAAA
  • fcc.gov/MX
  • fcc.gov/NS
  • fcc.gov/NSEC3PARAM
  • fcc.gov/SOA
  • fcc.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • fcc.gov/DNSKEY (alg 7, id 13924)
  • fcc.gov/DNSKEY (alg 7, id 20480)
  • fcc.gov/DNSKEY (alg 7, id 50330)
  • fcc.gov/DNSKEY (alg 7, id 60414)
  • fcc.gov/DS (alg 7, id 60414)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • 6s17a.y6diw.fcc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (34)
  • RRSIG fcc.gov/A alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/MX alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/NS alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/NSEC3PARAM alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/SOA alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/TXT alg 7, id 50330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • fcc.gov/DNSKEY (alg 7, id 13924): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
  • fcc.gov/DNSKEY (alg 7, id 20480): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
  • fcc.gov/DNSKEY (alg 7, id 50330): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
  • fcc.gov/DNSKEY (alg 7, id 60414): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
  • 6s17a.y6diw.fcc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fcc.gov/CDNSKEY 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