View on GitHub

DNSViz: A DNS visualization tool

purchasing.gov

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

RRset statusRRset status

Secure (6)
  • purchasing.gov/A
  • purchasing.gov/NS
  • purchasing.gov/NSEC3PARAM
  • purchasing.gov/SOA
  • purchasing.gov/SOA
  • purchasing.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (1)
  • purchasing.gov/DNSKEY (alg 7, id 6719)
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • purchasing.gov/DNSKEY (alg 7, id 17382)
  • purchasing.gov/DNSKEY (alg 7, id 5983)
  • purchasing.gov/DS (alg 7, id 5983)
  • purchasing.gov/DS (alg 7, id 5983)

Delegation statusDelegation status

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

NoticesNotices

Errors (12)
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: The Signature Expiration field of the RRSIG RR (2022-05-09 12:07:21+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: The Signature Expiration field of the RRSIG RR (2022-05-09 12:07:21+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: The Signature Expiration field of the RRSIG RR (2022-05-09 12:07:21+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: The Signature Expiration field of the RRSIG RR (2022-05-09 12:07:21+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: The Signature Expiration field of the RRSIG RR (2022-05-09 12:07:21+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: The Signature Expiration field of the RRSIG RR (2022-05-09 12:07:21+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • gov to purchasing.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. (56.0.82.25, UDP_-_EDNS0_4096_D_KN)
  • purchasing.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • purchasing.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ouwrgkdpjn.purchasing.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • purchasing.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • purchasing.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (26)
  • RRSIG purchasing.gov/A alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/DNSKEY alg 7, id 5983: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/NS alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/NSEC3PARAM alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/SOA alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/SOA alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG purchasing.gov/TXT alg 7, id 17382: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • purchasing.gov/DNSKEY (alg 7, id 6719): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (56.0.141.25, UDP_-_EDNS0_4096_D_KN)
  • purchasing.gov/DS (alg 7, id 5983): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • purchasing.gov/DS (alg 7, id 5983): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • purchasing.gov/DS (alg 7, id 5983): 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.
  • purchasing.gov/DS (alg 7, id 5983): 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.
  • purchasing.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • purchasing.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ouwrgkdpjn.purchasing.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • purchasing.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • purchasing.gov/AAAA 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