View on GitHub

DNSViz: A DNS visualization tool

bcfp.gov

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

RRset statusRRset status

Bogus (4)
  • bcfp.gov/A
  • bcfp.gov/NS
  • bcfp.gov/SOA
  • bcfp.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • bcfp.gov/DNSKEY (alg 7, id 12569)
  • bcfp.gov/DNSKEY (alg 7, id 24394)
  • bcfp.gov/DNSKEY (alg 7, id 31575)
  • bcfp.gov/DNSKEY (alg 7, id 4922)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • bcfp.gov/DS (alg 7, id 28134)
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • bcfp.gov/DNSKEY (alg 7, id 28134)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • gov to bcfp.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. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_K)
  • gov to bcfp.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (63.150.72.5, 208.44.130.121, 2001:428::7, 2001:428::8, UDP_-_EDNS0_4096_D_K)
  • bcfp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • h9n80ti4dp.bcfp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bcfp.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • bcfp.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
  • RRSIG bcfp.gov/A alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 24394: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 24394: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 24394: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 24394: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/DNSKEY alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/NS alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/SOA alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bcfp.gov/TXT alg 7, id 4922: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • bcfp.gov/DS (alg 7, id 28134): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bcfp.gov/DS (alg 7, id 28134): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bcfp.gov/DS (alg 7, id 28134): 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.
  • bcfp.gov/DS (alg 7, id 28134): 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.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • h9n80ti4dp.bcfp.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bcfp.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bcfp.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bcfp.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bcfp.gov/MX 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