View on GitHub

DNSViz: A DNS visualization tool

fpki.gov

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

RRset statusRRset status

Secure (3)
  • fpki.gov/NS
  • fpki.gov/NSEC3PARAM
  • fpki.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • fpki.gov/DNSKEY (alg 7, id 14604)
  • fpki.gov/DNSKEY (alg 7, id 27809)
  • fpki.gov/DNSKEY (alg 7, id 36909)
  • fpki.gov/DNSKEY (alg 7, id 39623)
  • fpki.gov/DS (alg 7, id 14604)
  • fpki.gov/DS (alg 7, id 14604)
  • fpki.gov/DS (alg 7, id 36909)
  • fpki.gov/DS (alg 7, id 36909)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • fpki.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:9b:c000:9200:12::30, 2620:9b:c001:9300:22::30)
  • fpki.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, 199.167.93.100, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • fpki.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:9b:c000:9200:12::30, 2620:9b:c001:9300:22::30, UDP_-_NOEDNS_)
  • fpki.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.93.100, UDP_-_NOEDNS_)
  • fpki.gov/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (199.167.92.100, 199.167.93.100, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • fpki.gov/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (199.167.92.100, TCP_-_NOEDNS_)
  • fpki.gov/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (199.167.92.100, 199.167.93.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • fpki.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (199.167.92.100, 199.167.93.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • fpki.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (199.167.92.100, TCP_-_EDNS0_4096_D_N)
  • fpki.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.93.100, UDP_-_NOEDNS_)
  • fpki.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, 199.167.93.100, UDP_-_NOEDNS_)
  • fpki.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • fpki.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • fpki.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 7bo9jpht5k.fpki.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • fpki.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • fpki.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (37)
  • RRSIG fpki.gov/DNSKEY alg 7, id 14604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 14604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 14604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 14604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 36909: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 36909: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 36909: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 36909: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/DNSKEY alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/NS alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/NS alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/NS alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/NS alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/NSEC3PARAM alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/NSEC3PARAM alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/SOA alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/SOA alg 7, id 27809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/SOA alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fpki.gov/SOA alg 7, id 39623: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • fpki.gov/DS (alg 7, id 14604): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fpki.gov/DS (alg 7, id 14604): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fpki.gov/DS (alg 7, id 14604): 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.
  • fpki.gov/DS (alg 7, id 14604): 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.
  • fpki.gov/DS (alg 7, id 36909): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fpki.gov/DS (alg 7, id 36909): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fpki.gov/DS (alg 7, id 36909): 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.
  • fpki.gov/DS (alg 7, id 36909): 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.
  • fpki.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fpki.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fpki.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