View on GitHub

DNSViz: A DNS visualization tool

foiaonline.gov

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

RRset statusRRset status

Insecure (6)
  • foiaonline.gov/A
  • foiaonline.gov/AAAA
  • foiaonline.gov/NS
  • foiaonline.gov/SOA
  • foiaonline.gov/SOA
  • foiaonline.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (1)
  • foiaonline.gov/DNSKEY (alg 8, id 59026)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of foiaonline.gov/DS
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to foiaonline.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (18)
  • NSEC3 proving non-existence of foiaonline.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of foiaonline.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG foiaonline.gov/DNSKEY alg 8, id 59026: With a TTL of 1296000 the RRSIG RR can be in the cache of a non-validating resolver until 5 days after it expires at 2021-03-10 19:21:17+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG foiaonline.gov/DNSKEY alg 8, id 59026: With a TTL of 1296000 the RRSIG RR can be in the cache of a non-validating resolver until 5 days after it expires at 2021-03-10 21:07:48+00:00. See RFC 4035, Sec. 5.3.3.
  • foiaonline.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c)
  • foiaonline.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c)
  • foiaonline.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
  • foiaonline.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
  • foiaonline.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • foiaonline.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
  • foiaonline.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, TCP_-_NOEDNS_)
  • foiaonline.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • foiaonline.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 161.80.212.12, 2620:117:506f:c::f00c, 2620:117:5071:d4::f00c, UDP_-_NOEDNS_)
  • foiaonline.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • foiaonline.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • foiaonline.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • foiaonline.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 7i5sf34wnj.foiaonline.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • NSEC3 proving non-existence of foiaonline.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of foiaonline.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • 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.
  • foiaonline.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • foiaonline.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 7i5sf34wnj.foiaonline.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • foiaonline.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