View on GitHub

DNSViz: A DNS visualization tool

polri.go.id

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

RRset statusRRset status

Secure (5)
  • polri.go.id/A
  • polri.go.id/MX
  • polri.go.id/NS
  • polri.go.id/SOA
  • polri.go.id/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (29)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • 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)
  • polri.go.id/DNSKEY (alg 8, id 28326)
  • polri.go.id/DNSKEY (alg 8, id 33618)
  • polri.go.id/DNSKEY (alg 8, id 37306)
  • polri.go.id/DNSKEY (alg 8, id 46305)
  • polri.go.id/DNSKEY (alg 8, id 52849)
  • polri.go.id/DS (alg 10, id 27582)
  • polri.go.id/DS (alg 5, id 16006)
  • polri.go.id/DS (alg 5, id 20851)
  • polri.go.id/DS (alg 5, id 32602)
  • polri.go.id/DS (alg 5, id 36757)
  • polri.go.id/DS (alg 5, id 51121)
  • polri.go.id/DS (alg 5, id 54928)
  • polri.go.id/DS (alg 5, id 667)
  • polri.go.id/DS (alg 5, id 9886)
  • polri.go.id/DS (alg 8, id 31582)
  • polri.go.id/DS (alg 8, id 37306)
  • polri.go.id/DS (alg 8, id 37306)
  • polri.go.id/DS (alg 8, id 52849)
  • polri.go.id/DS (alg 8, id 52849)
  • polri.go.id/DS (alg 8, id 54619)
  • polri.go.id/DS (alg 8, id 62776)
Non_existent (12)
  • polri.go.id/DNSKEY (alg 10, id 27582)
  • polri.go.id/DNSKEY (alg 5, id 16006)
  • polri.go.id/DNSKEY (alg 5, id 20851)
  • polri.go.id/DNSKEY (alg 5, id 32602)
  • polri.go.id/DNSKEY (alg 5, id 36757)
  • polri.go.id/DNSKEY (alg 5, id 51121)
  • polri.go.id/DNSKEY (alg 5, id 54928)
  • polri.go.id/DNSKEY (alg 5, id 667)
  • polri.go.id/DNSKEY (alg 5, id 9886)
  • polri.go.id/DNSKEY (alg 8, id 31582)
  • polri.go.id/DNSKEY (alg 8, id 54619)
  • polri.go.id/DNSKEY (alg 8, id 62776)

Delegation statusDelegation status

Secure (3)
  • . to id
  • go.id to polri.go.id
  • id to go.id

NoticesNotices

Errors (30)
  • go.id to polri.go.id: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • go.id to polri.go.id: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (120.29.231.234)
  • polri.go.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (120.29.231.234, UDP_-_NOEDNS_)
  • polri.go.id/A: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN)
  • polri.go.id/A: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 28326): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 28326): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 33618): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 33618): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 37306): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 37306): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 46305): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 46305): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 52849): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/DNSKEY (alg 8, id 52849): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_KN)
  • polri.go.id/MX: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • polri.go.id/MX: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • polri.go.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (120.29.231.234, UDP_-_NOEDNS_)
  • polri.go.id/NS: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN)
  • polri.go.id/NS: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN)
  • polri.go.id/SOA: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • polri.go.id/SOA: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • polri.go.id/TXT: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN)
  • polri.go.id/TXT: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.12, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_KN)
  • 1gqi76fuas.polri.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • polri.go.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • polri.go.id/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • polri.go.id/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • polri.go.id/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (58)
  • 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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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 polri.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.
  • go.id to polri.go.id: The following NS name(s) were found in the delegation NS RRset (i.e., in the go.id zone), but not in the authoritative NS RRset: ns8.polri.go.id See RFC 1034, Sec. 4.2.2.
  • polri.go.id/DS (alg 5, id 16006): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 16006): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 16006): 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.
  • polri.go.id/DS (alg 5, id 16006): 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.
  • polri.go.id/DS (alg 5, id 36757): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 36757): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 36757): 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.
  • polri.go.id/DS (alg 5, id 36757): 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.
  • polri.go.id/DS (alg 5, id 54928): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 54928): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 54928): 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.
  • polri.go.id/DS (alg 5, id 54928): 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.
  • polri.go.id/DS (alg 5, id 667): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 667): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 667): 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.
  • polri.go.id/DS (alg 5, id 667): 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.
  • polri.go.id/DS (alg 5, id 9886): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 9886): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 5, id 9886): 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.
  • polri.go.id/DS (alg 5, id 9886): 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.
  • polri.go.id/DS (alg 8, id 31582): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 31582): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 31582): 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.
  • polri.go.id/DS (alg 8, id 31582): 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.
  • polri.go.id/DS (alg 8, id 37306): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 37306): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 37306): 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.
  • polri.go.id/DS (alg 8, id 37306): 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.
  • polri.go.id/DS (alg 8, id 52849): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 52849): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 52849): 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.
  • polri.go.id/DS (alg 8, id 52849): 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.
  • polri.go.id/DS (alg 8, id 54619): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 54619): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • polri.go.id/DS (alg 8, id 54619): 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.
  • polri.go.id/DS (alg 8, id 54619): 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.
  • polri.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