nationalresourcedirectory.gov
Updated:
2020-07-02 11:23:08 UTC (1603 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- nationalresourcedirectory.gov/A
- nationalresourcedirectory.gov/AAAA
- nationalresourcedirectory.gov/MX
- nationalresourcedirectory.gov/NS
- nationalresourcedirectory.gov/SOA
- nationalresourcedirectory.gov/TXT
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- ./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)
- nationalresourcedirectory.gov/DNSKEY (alg 8, id 13716)
- nationalresourcedirectory.gov/DNSKEY (alg 8, id 17893)
- nationalresourcedirectory.gov/DNSKEY (alg 8, id 2531)
- nationalresourcedirectory.gov/DNSKEY (alg 8, id 42616)
- nationalresourcedirectory.gov/DS (alg 8, id 2531)
- nationalresourcedirectory.gov/DS (alg 8, id 2531)
- nationalresourcedirectory.gov/DS (alg 8, id 42616)
- nationalresourcedirectory.gov/DS (alg 8, id 42616)
Delegation status
Secure (2)
- . to gov
- gov to nationalresourcedirectory.gov
Notices
Errors (2)
- rgixta12qh.nationalresourcedirectory.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nationalresourcedirectory.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- 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.
- nationalresourcedirectory.gov/DS (alg 8, id 2531): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nationalresourcedirectory.gov/DS (alg 8, id 2531): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nationalresourcedirectory.gov/DS (alg 8, id 2531): 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.
- nationalresourcedirectory.gov/DS (alg 8, id 2531): 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.
- nationalresourcedirectory.gov/DS (alg 8, id 42616): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nationalresourcedirectory.gov/DS (alg 8, id 42616): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nationalresourcedirectory.gov/DS (alg 8, id 42616): 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.
- nationalresourcedirectory.gov/DS (alg 8, id 42616): 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.
- rgixta12qh.nationalresourcedirectory.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nationalresourcedirectory.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
