View on GitHub

DNSViz: A DNS visualization tool

polkam.go.id

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (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
Secure (2)
  • go.id/SOA
  • go.id/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • polkam.go.id/DNSKEY (alg 13, id 2371)
  • polkam.go.id/DNSKEY (alg 13, id 34505)
Secure (9)
  • ./DNSKEY (alg 8, id 20038)
  • ./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 statusDelegation status

Insecure (1)
  • go.id to polkam.go.id
Secure (2)
  • . to id
  • id to go.id

NoticesNotices

Errors (4)
  • go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:b::b, 2402:ee80:c::c)
  • id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:b::b, 2402:ee80:c::c)
  • polkam.go.id/CDNSKEY: The CDNSKEY RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
  • polkam.go.id/CDS: The CDS RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
Warnings (8)
  • 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.
  • 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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph