polri.go.id

Updated: 2023-08-17 12:57:35 UTC (498 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset 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 status

Secure (26)

./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
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 17454)
polri.go.id/DNSKEY (alg 8, id 31582)
polri.go.id/DNSKEY (alg 8, id 32304)
polri.go.id/DNSKEY (alg 8, id 48330)
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 31582)
polri.go.id/DS (alg 8, id 54619)
polri.go.id/DS (alg 8, id 62776)

Non_existent (11)

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 54619)
polri.go.id/DNSKEY (alg 8, id 62776)

Delegation status

Secure (3)

. to id
go.id to polri.go.id
id to go.id

Notices

Errors (41)

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)
go.id zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:df5:4000:4::4)
go.id zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (45.126.57.57)
go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:c::c, 2402:ee80:d::d)
go.id/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (45.126.57.57, TCP_-_EDNS0_4096_D_KN)
go.id/DNSKEY: No response was received from the server over UDP (tried 10 times). See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, UDP_-_EDNS0_4096_D_KN)
go.id/DNSKEY: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (103.19.177.177, UDP_-_EDNS0_4096_D_KN)
id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:c::c, 2402:ee80:d::d)
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 17454): 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 17454): 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 31582): 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 31582): 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 32304): 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 32304): 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 48330): 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 48330): 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/DS: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (45.126.57.57, 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 TCP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, TCP_-_EDNS0_4096_D)
polri.go.id/NS: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (45.126.57.57, TCP_-_EDNS0_4096_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)
polri.go.id/DNSKEY 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/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.
9nzdst1p6k.polri.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
polri.go.id/DS 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.
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 32602): 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 32602): 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 32602): 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 32602): 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 51121): 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 51121): 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 51121): 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 51121): 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 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 (alg 8, id 62776): 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 62776): 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 62776): 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 62776): 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.