polkam.go.id
Updated:
2021-10-28 13:20:15 UTC (3 years ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- polkam.go.id/A
- polkam.go.id/AAAA
- polkam.go.id/NS
- polkam.go.id/SOA
- polkam.go.id/TXT
Secure (1)
- go.id/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- NSEC proving non-existence of polkam.go.id/DS
- go.id/DNSKEY (alg 10, id 25427)
- go.id/DNSKEY (alg 10, id 48051)
- go.id/DS (alg 10, id 48051)
- id/DNSKEY (alg 8, id 22449)
- id/DNSKEY (alg 8, id 26887)
- id/DS (alg 8, id 26887)
Delegation status
Insecure (1)
- go.id to polkam.go.id
Secure (2)
- . to id
- id to go.id
Notices
Warnings (7)
- RRSIG NSEC proving non-existence of polkam.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG go.id/SOA alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- polkam.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
