korlantas.polri.go.id

Updated: 2021-02-02 08:33:53 UTC (1419 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

Insecure (3)

korlantas.polri.go.id/A
korlantas.polri.go.id/NS
korlantas.polri.go.id/SOA

Secure (1)

polri.go.id/SOA

DNSKEY/DS/NSEC status

Secure (26)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
NSEC proving non-existence of korlantas.polri.go.id/DS
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/DNSKEY (alg 5, id 11346)
polri.go.id/DNSKEY (alg 5, id 25026)
polri.go.id/DNSKEY (alg 5, id 36757)
polri.go.id/DNSKEY (alg 5, id 47253)
polri.go.id/DNSKEY (alg 5, id 9886)
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 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 5, id 9886)

Non_existent (6)

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 51121)
polri.go.id/DNSKEY (alg 5, id 54928)
polri.go.id/DNSKEY (alg 5, id 667)

Delegation status

Insecure (1)

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

Secure (3)

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

Notices

Errors (3)

korlantas.polri.go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (120.29.226.226, 120.29.231.231)
korlantas.polri.go.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (120.29.226.226, 120.29.231.231, UDP_-_NOEDNS_)
korlantas.polri.go.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (120.29.226.226, 120.29.231.231, UDP_-_NOEDNS_)

Warnings (70)

RRSIG NSEC proving non-existence of korlantas.polri.go.id/DS alg 5, id 11346: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). 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 polri.go.id/DNSKEY alg 5, id 11346: 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 11346: 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 11346: 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 11346: 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 11346: 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 9886: 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 9886: 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 9886: 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 9886: 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 9886: 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/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/SOA alg 5, id 11346: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
go.id/DNSKEY (alg 10, id 25427): 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. (103.19.177.177, UDP_-_EDNS0_4096_D_KN)
go.id/DNSKEY (alg 10, id 48051): 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. (103.19.177.177, UDP_-_EDNS0_4096_D_KN)
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/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.
korlantas.polri.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.