uam.es | DNSViz

uam.es

Updated: 2024-01-20 11:46:25 UTC (308 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)

uam.es/A
uam.es/MX
uam.es/NS
uam.es/SOA
uam.es/TXT

Secure (1)

es/SOA

DNSKEY/DS/NSEC status

Secure (6)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 30903)
NSEC3 proving non-existence of uam.es/DS
es/DNSKEY (alg 8, id 44375)
es/DNSKEY (alg 8, id 61351)
es/DS (alg 8, id 44375)

Delegation status

Insecure (1)

es to uam.es

Secure (1)

. to es

Notices

Errors (3)

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

Warnings (3)

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