anonaddy.me
Updated:
2021-08-25 16:16:54 UTC (968 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- anonaddy.me/A
- anonaddy.me/AAAA
- anonaddy.me/MX
- anonaddy.me/NS
- anonaddy.me/NSEC3PARAM
- anonaddy.me/SOA
- anonaddy.me/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- anonaddy.me/DNSKEY (alg 13, id 41296)
- anonaddy.me/DS (alg 13, id 41296)
- anonaddy.me/DS (alg 13, id 41296)
- me/DNSKEY (alg 8, id 3228)
- me/DNSKEY (alg 8, id 43188)
- me/DNSKEY (alg 8, id 45352)
- me/DS (alg 8, id 45352)
Delegation status
Secure (2)
- . to me
- me to anonaddy.me
Notices
Warnings (6)
- anonaddy.me/DS (alg 13, id 41296): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- anonaddy.me/DS (alg 13, id 41296): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- anonaddy.me/DS (alg 13, id 41296): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- anonaddy.me/DS (alg 13, id 41296): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- anonaddy.me/DS (alg 13, id 41296): 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.
- anonaddy.me/DS (alg 13, id 41296): 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.
JavaScript is required to make the graph below interactive.
