tniad.mil.id
Updated:
2022-12-14 16:59:27 UTC (1120 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- tniad.mil.id/A
- tniad.mil.id/AAAA
- tniad.mil.id/MX
- tniad.mil.id/NS
- tniad.mil.id/SOA
- tniad.mil.id/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- id/DNSKEY (alg 8, id 22449)
- id/DNSKEY (alg 8, id 26887)
- id/DS (alg 8, id 26887)
- mil.id/DNSKEY (alg 10, id 23342)
- mil.id/DNSKEY (alg 10, id 27192)
- mil.id/DS (alg 10, id 27192)
- tniad.mil.id/DNSKEY (alg 13, id 47259)
- tniad.mil.id/DNSKEY (alg 13, id 58974)
- tniad.mil.id/DS (alg 13, id 47259)
Delegation status
Secure (3)
- . to id
- id to mil.id
- mil.id to tniad.mil.id
Notices
Warnings (6)
- RRSIG mil.id/DNSKEY alg 10, id 23342: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG mil.id/DNSKEY alg 10, id 23342: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG mil.id/DNSKEY alg 10, id 27192: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG mil.id/DNSKEY alg 10, id 27192: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG tniad.mil.id/DS alg 10, id 23342: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- tniad.mil.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
