reliablesuccess.xyz
Updated:
2020-04-12 23:03:18 UTC (1714 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- reliablesuccess.xyz/A (NXDOMAIN)
Secure (1)
- xyz/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of reliablesuccess.xyz/A
- xyz/DNSKEY (alg 8, id 3599)
- xyz/DNSKEY (alg 8, id 37419)
- xyz/DNSKEY (alg 8, id 64504)
- xyz/DS (alg 8, id 3599)
- xyz/DS (alg 8, id 3599)
Delegation status
Secure (1)
- . to xyz
Notices
Errors (3)
- NSEC3 proving non-existence of reliablesuccess.xyz/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of reliablesuccess.xyz/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- xyz/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- xyz/DS (alg 8, id 3599): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- xyz/DS (alg 8, id 3599): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- xyz/DS (alg 8, id 3599): 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.
- xyz/DS (alg 8, id 3599): 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.
JavaScript is required to make the graph below interactive.
