gsc-enhancements.site
Updated:
2023-10-18 15:43:51 UTC (355 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- gsc-enhancements.site/A
- gsc-enhancements.site/AAAA
- gsc-enhancements.site/NS
- gsc-enhancements.site/SOA
- gsc-enhancements.site/TXT
Secure (1)
- site/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- gsc-enhancements.site/DNSKEY (alg 13, id 2371)
- gsc-enhancements.site/DNSKEY (alg 13, id 34505)
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of gsc-enhancements.site/DS
- site/DNSKEY (alg 8, id 25839)
- site/DNSKEY (alg 8, id 4459)
- site/DNSKEY (alg 8, id 51676)
- site/DS (alg 8, id 51676)
- site/DS (alg 8, id 51676)
Delegation status
Insecure (1)
- site to gsc-enhancements.site
Secure (1)
- . to site
Notices
Warnings (4)
- site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- site/DS (alg 8, id 51676): 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.
- site/DS (alg 8, id 51676): 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.
