View on GitHub
3m.com
Updated:
2024-06-27 07:46:19 UTC
(
72 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
(5)
3m.com/A
3m.com/MX
3m.com/NS
3m.com/SOA
3m.com/TXT
Secure
(2)
com/SOA
com/SOA
DNSKEY/DS/NSEC status
Secure
(7)
./DNSKEY (alg 8, id 20038)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 5613)
NSEC3 proving non-existence of 3m.com/DS
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 956)
com/DS (alg 13, id 19718)
Delegation status
Insecure
(1)
com to 3m.com
Secure
(1)
. to com
Notices
Warnings
(2)
com to 3m.com: Authoritative AAAA records exist for a.ns.3m.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
com to 3m.com: Authoritative AAAA records exist for b.ns.3m.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
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.