View on GitHub

DNSViz: A DNS visualization tool

coronavirus.gov

Updated: 2020-03-13 17:16:54 UTC (1713 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

Insecure (4)
  • coronavirus.gov/A
  • coronavirus.gov/AAAA
  • coronavirus.gov/NS
  • coronavirus.gov/SOA
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • coronavirus.gov/DNSKEY (alg 13, id 5288)
  • coronavirus.gov/DNSKEY (alg 13, id 62193)
  • coronavirus.gov/DNSKEY (alg 13, id 64693)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • NSEC3 proving non-existence of coronavirus.gov/DS
  • gov/DNSKEY (alg 8, id 36558)
  • 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 coronavirus.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (8)
  • NSEC3 proving non-existence of coronavirus.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 coronavirus.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:74:29::2:30)
  • coronavirus.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • l8hf7p2m4s.coronavirus.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • coronavirus.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • coronavirus.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • coronavirus.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • NSEC3 proving non-existence of coronavirus.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of coronavirus.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.
  • coronavirus.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • l8hf7p2m4s.coronavirus.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coronavirus.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coronavirus.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coronavirus.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