lkpp.go.id
Updated:
2022-06-28 01:36:33 UTC (831 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- lkpp.go.id/A
- lkpp.go.id/MX
- lkpp.go.id/NS
- lkpp.go.id/SOA
- lkpp.go.id/SOA
- lkpp.go.id/SOA
- lkpp.go.id/TXT
Secure (1)
- go.id/SOA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- ./DNSKEY (alg 8, id 47671)
- NSEC proving non-existence of lkpp.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 status
Insecure (1)
- go.id to lkpp.go.id
Secure (2)
- . to id
- id to go.id
Notices
Errors (5)
- 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)
- 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)
- lkpp.go.id zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (103.13.181.25, 103.13.181.26, 103.13.181.28, 180.233.156.19)
- lkpp.go.id/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (180.233.156.19, TCP_-_EDNS0_4096_D_N)
- lkpp.go.id/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (103.13.181.25, 103.13.181.26, 103.13.181.28, TCP_-_EDNS0_4096_D_N)
Warnings (11)
- RRSIG NSEC proving non-existence of lkpp.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.
- go.id to lkpp.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: ns4.lkpp.go.id, ns5.lkpp.go.id, ns6.lkpp.go.id See RFC 1034, Sec. 4.2.2.
- go.id to lkpp.go.id: The glue address(es) for ns2.lkpp.go.id (103.55.160.78) differed from its authoritative address(es) (103.13.181.24). See RFC 1034, Sec. 4.2.2.
- go.id to lkpp.go.id: The glue address(es) for ns3.lkpp.go.id (103.13.181.25) differed from its authoritative address(es) (103.55.160.78). See RFC 1034, Sec. 4.2.2.
- go.id to lkpp.go.id: The glue address(es) for ns4.lkpp.go.id (103.13.181.24) differed from its authoritative address(es) (103.13.181.25). See RFC 1034, Sec. 4.2.2.
- lkpp.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
