polri.go.id

Updated: 2020-04-22 03:03:03 UTC (1727 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

Bogus (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

Bogus (6)

polri.go.id/DNSKEY (alg 5, id 1206)
polri.go.id/DNSKEY (alg 5, id 18813)
polri.go.id/DNSKEY (alg 5, id 32602)
polri.go.id/DNSKEY (alg 5, id 36757)
polri.go.id/DNSKEY (alg 5, id 47337)
polri.go.id/DNSKEY (alg 5, id 54928)

Secure (13)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 48903)
go.id/DNSKEY (alg 10, id 25427)
go.id/DNSKEY (alg 10, id 48051)
go.id/DS (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)
id/DS (alg 8, id 26887)
polri.go.id/DS (alg 5, id 16006)
polri.go.id/DS (alg 5, id 20851)
polri.go.id/DS (alg 5, id 54928)

Non_existent (2)

polri.go.id/DNSKEY (alg 5, id 16006)
polri.go.id/DNSKEY (alg 5, id 20851)

Delegation status

Bogus (1)

go.id to polri.go.id

Secure (2)

. to id
id to go.id

Notices

Errors (1)

go.id to polri.go.id: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (120.29.225.225, 120.29.226.226, 120.29.228.228, 120.29.230.230, 120.29.231.231, TCP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K)

Warnings (63)

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/A alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 32602: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 32602: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 32602: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 32602: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 32602: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 32602: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 36757: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 36757: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 36757: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 36757: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 36757: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 36757: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 54928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 54928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 54928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 54928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 54928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/DNSKEY alg 5, id 54928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). 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/MX alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/NS alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/SOA alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG polri.go.id/TXT alg 5, id 47337: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
go.id/DS (alg 10, id 48051): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
go.id/DS (alg 10, id 48051): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
go.id/DS (alg 10, id 48051): 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.
go.id/DS (alg 10, id 48051): 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.
id/DS (alg 8, id 26887): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
id/DS (alg 8, id 26887): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
id/DS (alg 8, id 26887): 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.
id/DS (alg 8, id 26887): 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/DNSKEY (alg 5, id 1206): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.225.225, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_K)
polri.go.id/DNSKEY (alg 5, id 18813): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.225.225, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_K)
polri.go.id/DNSKEY (alg 5, id 32602): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.225.225, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_K)
polri.go.id/DNSKEY (alg 5, id 36757): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.225.225, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_K)
polri.go.id/DNSKEY (alg 5, id 47337): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.225.225, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_K)
polri.go.id/DNSKEY (alg 5, id 54928): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.225.225, 120.29.228.228, 120.29.230.230, UDP_-_EDNS0_4096_D_K)
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 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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
polri.go.id/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
polri.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
ycoe93ismv.polri.go.id/A has warnings; select the "Denial of existence" DNSSEC option to see them.
polri.go.id/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.