migadu.com
Updated:
2023-12-09 04:17:11 UTC (784 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- migadu.com/A
- migadu.com/AAAA
- migadu.com/MX
- migadu.com/NS
- migadu.com/SOA
- migadu.com/SOA
- migadu.com/SOA
- migadu.com/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 46171)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 63246)
- com/DS (alg 13, id 19718)
- migadu.com/DNSKEY (alg 13, id 48892)
- migadu.com/DS (alg 13, id 48892)
- migadu.com/DS (alg 13, id 48892)
Delegation status
Secure (2)
- . to com
- com to migadu.com
Notices
Errors (1)
- migadu.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:41d0:a:626c::1, UDP_-_NOEDNS_)
Warnings (6)
- migadu.com/DS (alg 13, id 48892): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- migadu.com/DS (alg 13, id 48892): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- migadu.com/DS (alg 13, id 48892): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- migadu.com/DS (alg 13, id 48892): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- migadu.com/DS (alg 13, id 48892): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
- migadu.com/DS (alg 13, id 48892): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
