cran.na | DNSViz

cran.na

Updated: 2024-01-19 08:46:31 UTC (351 days ago) Update now

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)

cran.na/A
cran.na/MX
cran.na/NS
cran.na/SOA
cran.na/TXT

Secure (2)

na/SOA
na/SOA

DNSKEY/DS/NSEC status

Secure (6)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 30903)
NSEC3 proving non-existence of cran.na/DS
na/DNSKEY (alg 8, id 25079)
na/DNSKEY (alg 8, id 58846)
na/DS (alg 8, id 25079)

Delegation status

Insecure (1)

na to cran.na

Secure (1)

. to na

Notices

Errors (3)

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

Warnings (3)

NSEC3 proving non-existence of cran.na/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of cran.na/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
cran.na/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