View on GitHub
uio.no
Updated:
2023-07-28 05:54:12 UTC
(
496 days ago
)
Go to most recent »
« Previous analysis
|
Next analysis »
Tweet
DNSSEC
Responses
Servers
Analyze
DNSSEC options (
hide
)
|?|
RR types:
--All--
A
AAAA
TXT
PTR
MX
NS
SOA
CNAME
SRV
NAPTR
TLSA
NSEC3PARAM
CDNSKEY
CDS
CAA
|?|
DNSSEC algorithms:
--All--
1 - RSA/MD5
3 - DSA/SHA1
5 - RSA/SHA-1
6 - DSA-NSEC3-SHA1
7 - RSASHA1-NSEC3-SHA1
8 - RSA/SHA-256
10 - RSA/SHA-512
12 - GOST R 34.10-2001
13 - ECDSA Curve P-256 with SHA-256
14 - ECDSA Curve P-384 with SHA-384
15 - Ed25519
16 - Ed448
|?|
DS digest algorithms:
--All--
1 - SHA-1
2 - SHA-256
3 - GOST R 34.11-94
4 - SHA-384
|?|
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
(6)
uio.no/A
uio.no/AAAA
uio.no/MX
uio.no/NS
uio.no/SOA
uio.no/TXT
Secure
(1)
no/SOA
DNSKEY/DS/NSEC status
Secure
(6)
./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of uio.no/DS
no/DNSKEY (alg 13, id 37317)
no/DNSKEY (alg 13, id 38032)
no/DS (alg 13, id 38032)
Delegation status
Insecure
(1)
no to uio.no
Secure
(1)
. to no
Notices
Warnings
(3)
NSEC3 proving non-existence of uio.no/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uio.no/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
uio.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
JavaScript is required to make the graph below interactive.