nrd.gov

Updated: 2020-04-09 13:54:09 UTC (1690 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 (5)

nrd.gov/A
nrd.gov/MX
nrd.gov/NS
nrd.gov/SOA
nrd.gov/TXT

DNSKEY/DS/NSEC status

Bogus (4)

nrd.gov/DNSKEY (alg 8, id 17133)
nrd.gov/DNSKEY (alg 8, id 37234)
nrd.gov/DNSKEY (alg 8, id 60348)
nrd.gov/DNSKEY (alg 8, id 65194)

Secure (11)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 33853)
./DNSKEY (alg 8, id 48903)
gov/DNSKEY (alg 8, id 36558)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
gov/DS (alg 8, id 7698)
nrd.gov/DS (alg 8, id 12760)
nrd.gov/DS (alg 8, id 13355)
nrd.gov/DS (alg 8, id 20024)
nrd.gov/DS (alg 8, id 31024)

Non_existent (4)

nrd.gov/DNSKEY (alg 8, id 12760)
nrd.gov/DNSKEY (alg 8, id 13355)
nrd.gov/DNSKEY (alg 8, id 20024)
nrd.gov/DNSKEY (alg 8, id 31024)

Delegation status

Bogus (1)

gov to nrd.gov

Secure (1)

. to gov

Notices

Errors (15)

gov to nrd.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. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
gov to nrd.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. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/DNSKEY (alg 8, id 17133): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/DNSKEY (alg 8, id 37234): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/DNSKEY (alg 8, id 60348): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/DNSKEY (alg 8, id 65194): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
nrd.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
nrd.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
nrd.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.222.56.242, 52.222.67.179, UDP_-_EDNS0_4096_D_K)
g3h67ib8zt.nrd.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
nrd.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
nrd.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
nrd.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (12)

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.
nrd.gov/DS (alg 8, id 12760): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nrd.gov/DS (alg 8, id 12760): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nrd.gov/DS (alg 8, id 12760): 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.
nrd.gov/DS (alg 8, id 12760): 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.
nrd.gov/DS (alg 8, id 20024): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nrd.gov/DS (alg 8, id 20024): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nrd.gov/DS (alg 8, id 20024): 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.
nrd.gov/DS (alg 8, id 20024): 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.