dds.mil | DNSViz

dds.mil

Updated: 2023-04-05 17:38:58 UTC (632 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

Insecure (5)

dds.mil/A
dds.mil/MX
dds.mil/NS
dds.mil/SOA
dds.mil/TXT

Secure (1)

mil/SOA

DNSKEY/DS/NSEC status

Secure (8)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
./DNSKEY (alg 8, id 951)
NSEC3 proving non-existence of dds.mil/DS
mil/DNSKEY (alg 8, id 53035)
mil/DNSKEY (alg 8, id 62470)
mil/DNSKEY (alg 8, id 8715)
mil/DS (alg 8, id 62470)

Delegation status

Insecure (1)

mil to dds.mil

Secure (1)

. to mil

Notices

Errors (3)

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

Warnings (3)

NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dds.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph