nationalguard.mil

Updated: 2020-05-17 17:42:19 UTC (1683 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 (3)

nationalguard.mil/NS
nationalguard.mil/SOA
nationalguard.mil/TXT

Secure (1)

mil/SOA

DNSKEY/DS/NSEC status

Bogus (5)

nationalguard.mil/DNSKEY (alg 8, id 11100)
nationalguard.mil/DNSKEY (alg 8, id 22436)
nationalguard.mil/DNSKEY (alg 8, id 44055)
nationalguard.mil/DNSKEY (alg 8, id 55712)
nationalguard.mil/DNSKEY (alg 8, id 59184)

Secure (9)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 48903)
NSEC3 proving non-existence of nationalguard.mil/DS
mil/DNSKEY (alg 8, id 47763)
mil/DNSKEY (alg 8, id 48726)
mil/DNSKEY (alg 8, id 7765)
mil/DS (alg 8, id 7765)
mil/DS (alg 8, id 7765)
nationalguard.mil/DS (alg 8, id 10105)

Non_existent (1)

nationalguard.mil/DNSKEY (alg 8, id 10105)

Delegation status

Bogus (1)

mil to nationalguard.mil

Secure (1)

. to mil

Notices

Errors (10)

NSEC3 proving non-existence of nationalguard.mil/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 nationalguard.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
mil to nationalguard.mil: 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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_K)
mil to nationalguard.mil: 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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_K)
nationalguard.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
214fqjtax6.nationalguard.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (16)

NSEC3 proving non-existence of nationalguard.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of nationalguard.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 7765): 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.
mil/DS (alg 8, id 7765): 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.
nationalguard.mil/DS (alg 8, id 10105): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nationalguard.mil/DS (alg 8, id 10105): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nationalguard.mil/DS (alg 8, id 10105): 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.
nationalguard.mil/DS (alg 8, id 10105): 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.
nationalguard.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
214fqjtax6.nationalguard.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
nationalguard.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.