View on GitHub

DNSViz: A DNS visualization tool

permanent.access.gpo.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

Bogus (1)
  • permanent.access.gpo.gov/A

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • NSEC3 proving non-existence of access.gpo.gov/DS
  • NSEC3 proving non-existence of access.gpo.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)
  • gpo.gov/DNSKEY (alg 8, id 11991)
  • gpo.gov/DNSKEY (alg 8, id 51334)
  • gpo.gov/DS (alg 8, id 51334)
  • gpo.gov/DS (alg 8, id 51334)

Delegation statusDelegation status

Bogus (1)
  • gpo.gov to access.gpo.gov
Secure (2)
  • . to gov
  • gov to gpo.gov

NoticesNotices

Errors (16)
  • NSEC3 proving non-existence of access.gpo.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 access.gpo.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 access.gpo.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 access.gpo.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 access.gpo.gov/DS: No NSEC3 RR matches the SNAME (access.gpo.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of access.gpo.gov/DS: No NSEC3 RR matches the SNAME (access.gpo.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of access.gpo.gov/DS: No NSEC3 RR matches the SNAME (access.gpo.gov). See RFC 5155, Sec. 8.6.
  • NSEC3 proving non-existence of access.gpo.gov/DS: No NSEC3 RR matches the SNAME (access.gpo.gov). See RFC 5155, Sec. 8.6.
  • RRSIG permanent.access.gpo.gov/A alg 8, id 11991: The Signer's Name field of the RRSIG RR (gpo.gov) does not match the name of the zone containing the RRset (access.gpo.gov). See RFC 4035, Sec. 5.3.1.
  • RRSIG permanent.access.gpo.gov/A alg 8, id 11991: The Signer's Name field of the RRSIG RR (gpo.gov) does not match the name of the zone containing the RRset (access.gpo.gov). See RFC 4035, Sec. 5.3.1.
  • access.gpo.gov/DNSKEY: The response (456 bytes) was malformed. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_512_D_K)
  • gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:74:29::2:30)
  • gpo.gov to access.gpo.gov: The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_K)
  • gpo.gov/DNSKEY: The response (449 bytes) was malformed. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_512_D_K)
  • access.gpo.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • permanent.access.gpo.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • NSEC3 proving non-existence of access.gpo.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of access.gpo.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of access.gpo.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of access.gpo.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 8, id 11991: The value of the Signature Inception field of the RRSIG RR (2020-03-13 15:01:25+00:00) is within possible clock skew range (17 seconds) of the current time (2020-03-13 15:01:42+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 8, id 11991: The value of the Signature Inception field of the RRSIG RR (2020-03-13 15:01:25+00:00) is within possible clock skew range (17 seconds) of the current time (2020-03-13 15:01:42+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.
  • access.gpo.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • permanent.access.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