View on GitHub

DNSViz: A DNS visualization tool

gpo.gov

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

RRset statusRRset status

Secure (5)
  • gpo.gov/A
  • gpo.gov/MX
  • gpo.gov/NS
  • gpo.gov/SOA
  • gpo.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gpo.gov/DNSKEY (alg 8, id 18651)
  • gpo.gov/DNSKEY (alg 8, id 44556)
  • gpo.gov/DNSKEY (alg 8, id 51334)
  • gpo.gov/DS (alg 8, id 51334)
  • gpo.gov/DS (alg 8, id 51334)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_EDNS0_512_D_K)
  • gpo.gov/DNSKEY: The response (321 bytes) was malformed. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_512_D_K)
  • gpo.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpo.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • uz3x0njks9.gpo.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpo.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (27)
  • ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • ./DNSKEY (alg 8, id 48903): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • RRSIG gpo.gov/DNSKEY alg 8, id 18651: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 18651: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 18651: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 44556: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 44556: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 44556: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 51334: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 51334: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/DNSKEY alg 8, id 51334: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:18:50+00:00) is within possible clock skew range (4 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/TXT alg 8, id 18651: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:19:54+00:00) is within possible clock skew range (3 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/TXT alg 8, id 18651: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:23:30+00:00) is within possible clock skew range (0 seconds) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/TXT alg 8, id 44556: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:19:54+00:00) is within possible clock skew range (3 minutes) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gpo.gov/TXT alg 8, id 44556: The value of the Signature Inception field of the RRSIG RR (2020-06-15 04:23:30+00:00) is within possible clock skew range (0 seconds) of the current time (2020-06-15 04:23:30+00:00). See RFC 4035, Sec. 5.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.
  • gpo.gov/DS (alg 8, id 51334): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gpo.gov/DS (alg 8, id 51334): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gpo.gov/DS (alg 8, id 51334): 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.
  • gpo.gov/DS (alg 8, id 51334): 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.
  • gpo.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpo.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uz3x0njks9.gpo.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpo.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