View on GitHub

DNSViz: A DNS visualization tool

dotgov.gov

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

RRset statusRRset status

Secure (9)
  • dotgov.gov/A
  • dotgov.gov/AAAA
  • dotgov.gov/MX
  • dotgov.gov/NS
  • dotgov.gov/NSEC3PARAM
  • dotgov.gov/NSEC3PARAM (NODATA)
  • dotgov.gov/SOA
  • dotgov.gov/SOA
  • dotgov.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (17)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC proving non-existence of dotgov.gov/NSEC3PARAM
  • dotgov.gov/DNSKEY (alg 8, id 22761)
  • dotgov.gov/DNSKEY (alg 8, id 35356)
  • dotgov.gov/DNSKEY (alg 8, id 55446)
  • dotgov.gov/DNSKEY (alg 8, id 9549)
  • dotgov.gov/DS (alg 8, id 35356)
  • dotgov.gov/DS (alg 8, id 9549)
  • dotgov.gov/DS (alg 8, id 9549)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 49735)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 64280)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • NSEC proving non-existence of dotgov.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: dotgov.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of dotgov.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: dotgov.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • RRSIG dotgov.gov/DNSKEY alg 8, id 35356: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG dotgov.gov/DNSKEY alg 8, id 35356: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG dotgov.gov/DNSKEY alg 8, id 35356: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • RRSIG dotgov.gov/DNSKEY alg 8, id 35356: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
  • dotgov.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • dotgov.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • mwd6bs3qfi.dotgov.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • dotgov.gov/DS (alg 8, id 9549): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dotgov.gov/DS (alg 8, id 9549): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dotgov.gov/DS (alg 8, id 9549): 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.
  • dotgov.gov/DS (alg 8, id 9549): 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/DNSKEY (alg 8, id 40921): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (69.36.153.30, 69.36.157.30, 81.19.194.30, 209.112.123.30, 2001:500:4431::2:30, 2620:74:27::2:30, 2620:74:28::2:30, 2620:74:29::2:30, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • dotgov.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mwd6bs3qfi.dotgov.gov/A 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