polkam.go.id
Updated:
2025-01-29 06:35:26 UTC (2 months ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- polkam.go.id/A
- polkam.go.id/AAAA
- polkam.go.id/CDNSKEY
- polkam.go.id/CDS
- polkam.go.id/MX
- polkam.go.id/NS
- polkam.go.id/SOA
- polkam.go.id/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26470)
- ./DNSKEY (alg 8, id 38696)
- 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)
- polkam.go.id/DNSKEY (alg 13, id 2371)
- polkam.go.id/DNSKEY (alg 13, id 34505)
- polkam.go.id/DS (alg 13, id 2371)
Delegation status
Secure (3)
- . to id
- go.id to polkam.go.id
- id to go.id
Notices
Errors (2)
- go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:d::d)
- id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:d::d)
Warnings (6)
- 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 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.
- 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.
