businessdefense.gov

Updated: 2021-01-05 11:25:58 UTC (1416 days ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26116)
./DNSKEY (alg 8, id 42351)
NSEC3 proving non-existence of businessdefense.gov/DS
gov/DNSKEY (alg 8, id 15489)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
gov/DS (alg 8, id 7698)

NSEC3 proving non-existence of businessdefense.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 businessdefense.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
businessdefense.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.

NSEC3 proving non-existence of businessdefense.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of businessdefense.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov to businessdefense.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns-1733.awsdns-24.co.uk, ns-1506.awsdns-60.org See RFC 1034, Sec. 4.2.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): 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.
businessdefense.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.