View on GitHub
gn
Updated:
2023-10-10 07:20:33 UTC
(
462 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
Secure
(3)
gn/NS
gn/SOA
gn/SOA
DNSKEY/DS/NSEC status
Secure
(9)
./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46780)
gn/DNSKEY (alg 8, id 21855)
gn/DNSKEY (alg 8, id 38486)
gn/DNSKEY (alg 8, id 4180)
gn/DNSKEY (alg 8, id 9311)
gn/DS (alg 8, id 38486)
gn/DS (alg 8, id 9311)
Delegation status
Secure
(1)
. to gn
Notices
Errors
(3)
gn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.216.168.49)
gn/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.216.168.49, UDP_-_NOEDNS_)
gn/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (147.28.0.39, TCP_-_EDNS0_4096_D_N)
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.