cyberthreat.id
Updated:
2020-11-03 08:46:29 UTC (1511 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- cyberthreat.id/A
- cyberthreat.id/AAAA
- cyberthreat.id/MX
- cyberthreat.id/NS
- cyberthreat.id/SOA
- cyberthreat.id/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- cyberthreat.id/DNSKEY (alg 8, id 24997)
- cyberthreat.id/DNSKEY (alg 8, id 64743)
- cyberthreat.id/DS (alg 8, id 24997)
- id/DNSKEY (alg 8, id 22449)
- id/DNSKEY (alg 8, id 26887)
- id/DS (alg 8, id 26887)
- id/DS (alg 8, id 26887)
Delegation status
Secure (2)
- . to id
- id to cyberthreat.id
Notices
Errors (2)
- t8gcd4amvy.cyberthreat.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
- cyberthreat.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- id/DS (alg 8, id 26887): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- id/DS (alg 8, id 26887): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- id/DS (alg 8, id 26887): 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.
- id/DS (alg 8, id 26887): 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.
- t8gcd4amvy.cyberthreat.id/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- cyberthreat.id/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
