uit.no | DNSViz

uit.no

Updated: 2021-05-20 12:04:18 UTC (1281 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)

uit.no/A
uit.no/MX
uit.no/NS
uit.no/SOA
uit.no/TXT

Secure (1)

no/SOA

DNSKEY/DS/NSEC status

Secure (7)

./DNSKEY (alg 8, id 14631)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of uit.no/DS
no/DNSKEY (alg 8, id 29471)
no/DNSKEY (alg 8, id 49683)
no/DNSKEY (alg 8, id 59643)
no/DS (alg 8, id 29471)

Delegation status

Insecure (1)

no to uit.no

Secure (1)

. to no

Notices

Errors (3)

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

Warnings (3)

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