View on GitHub

DNSViz: A DNS visualization tool

fcc.gov

Updated: 2024-03-21 16:49:12 UTC (120 days ago) Update now
« Previous analysis | Next analysis »
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 (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • ./DNSKEY (alg 8, id 5613)
  • fcc.gov/DNSKEY (alg 7, id 10452)
  • fcc.gov/DNSKEY (alg 7, id 13460)
  • fcc.gov/DNSKEY (alg 7, id 13924)
  • fcc.gov/DNSKEY (alg 7, id 60414)
  • fcc.gov/DS (alg 7, id 60414)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DS (alg 8, id 64280)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • fcc.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2600:1406:32::43)
  • fcc.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:1406:32::43, UDP_-_NOEDNS_)
  • fcc.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:1406:32::43, UDP_-_NOEDNS_)
  • f0shbcjo98.fcc.gov/A 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.
Warnings (28)
  • RRSIG fcc.gov/A alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/A alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/AAAA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 13924: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/DNSKEY alg 7, id 60414: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/MX alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/NS alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/NSEC3PARAM alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/SOA alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fcc.gov/TXT alg 7, id 10452: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • f0shbcjo98.fcc.gov/A 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.

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