permanent.access.gpo.gov

Updated: 2020-05-08 14:56:02 UTC (1641 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (1)

permanent.access.gpo.gov/A

DNSKEY/DS/NSEC status

Bogus (4)

NSEC3 proving non-existence of access.gpo.gov/DS
NSEC3 proving non-existence of access.gpo.gov/DS
access.gpo.gov/DNSKEY (alg 7, id 14946)
access.gpo.gov/DNSKEY (alg 7, id 2537)

Secure (10)

./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 4881)
gpo.gov/DNSKEY (alg 8, id 51334)
gpo.gov/DS (alg 8, id 51334)
gpo.gov/DS (alg 8, id 51334)

Delegation status

Bogus (1)

gpo.gov to access.gpo.gov

Secure (2)

. to gov
gov to gpo.gov

Notices

Errors (23)

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.
NSEC3 proving non-existence of access.gpo.gov/DS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.252.180, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.252.180, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.64.100, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.64.100, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.252.180, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.252.180, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.64.100, UDP_-_EDNS0_4096_D_K)
NSEC3 proving non-existence of access.gpo.gov/DS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.64.100, UDP_-_EDNS0_4096_D_K)
RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 7, id 2537: The Signer's Name field of the RRSIG RR (access.gpo.gov) does not match the name of the zone containing the RRset (gpo.gov). See RFC 4035, Sec. 5.3.1.
RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 7, id 2537: The Signer's Name field of the RRSIG RR (access.gpo.gov) does not match the name of the zone containing the RRset (gpo.gov). See RFC 4035, Sec. 5.3.1.
access.gpo.gov/DNSKEY: The response (488 bytes) was malformed. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_512_D_K)
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 (28)

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 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 7, id 2537: The value of the Signature Inception field of the RRSIG RR (2020-05-08 14:55:36+00:00) is within possible clock skew range (25 seconds) of the current time (2020-05-08 14:56:01+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG NSEC3 proving non-existence of access.gpo.gov/DS alg 7, id 2537: The value of the Signature Inception field of the RRSIG RR (2020-05-08 14:55:36+00:00) is within possible clock skew range (25 seconds) of the current time (2020-05-08 14:56:01+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 14946: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 14946: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 14946: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 14946: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG access.gpo.gov/DNSKEY alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG permanent.access.gpo.gov/A alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG permanent.access.gpo.gov/A alg 7, id 2537: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, 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.
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.