adr.gov
Updated:
2020-06-23 16:51:34 UTC (1615 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- adr.gov/A
- adr.gov/NS
- adr.gov/SOA
- adr.gov/TXT
DNSKEY/DS/NSEC status
Bogus (2)
- adr.gov/DNSKEY (alg 7, id 11360)
- adr.gov/DNSKEY (alg 7, id 37203)
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- ./DNSKEY (alg 8, id 48903)
- adr.gov/DS (alg 8, id 33919)
- adr.gov/DS (alg 8, id 4156)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (2)
- adr.gov/DNSKEY (alg 8, id 33919)
- adr.gov/DNSKEY (alg 8, id 4156)
Delegation status
Bogus (1)
- gov to adr.gov
Secure (1)
- . to gov
Notices
Errors (13)
- adr.gov/A: 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. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- adr.gov/DNSKEY (alg 7, id 11360): 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. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- adr.gov/DNSKEY (alg 7, id 37203): 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. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- adr.gov/NS: 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. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- adr.gov/SOA: 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. (96.127.44.178, 96.127.69.238, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- adr.gov/TXT: 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. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- gov to adr.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- gov to adr.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (96.127.44.178, 96.127.69.238, UDP_-_EDNS0_4096_D_K)
- adr.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- adr.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- ur17e6l8h5.adr.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- adr.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- adr.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
- RRSIG adr.gov/A alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/DNSKEY alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/DNSKEY alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/DNSKEY alg 7, id 37203: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/DNSKEY alg 7, id 37203: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/NS alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/SOA alg 7, id 11360: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG adr.gov/TXT alg 7, id 11360: 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.
- adr.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- adr.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- ur17e6l8h5.adr.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- adr.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- adr.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
