lkpp.go.id
Updated:
2020-05-25 14:40:44 UTC (1438 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- lkpp.go.id/A
- lkpp.go.id/MX
- lkpp.go.id/NS
- lkpp.go.id/SOA
- lkpp.go.id/TXT
Secure (1)
- go.id/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- 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)
- 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)
Delegation status
Insecure (1)
- go.id to lkpp.go.id
Secure (2)
- . to id
- id to go.id
Notices
Errors (12)
- lkpp.go.id zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. (103.55.160.78)
- lkpp.go.id zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. (103.55.160.78)
- lkpp.go.id zone: The server(s) were not responsive to queries over UDP. (103.55.160.20)
- lkpp.go.id/A: No response was received from the server over UDP (tried 12 times). (103.55.160.20, UDP_-_NOEDNS_)
- lkpp.go.id/A: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, UDP_-_NOEDNS_)
- lkpp.go.id/DNSKEY: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- lkpp.go.id/MX: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- lkpp.go.id/NS: No response was received from the server over UDP (tried 12 times). (103.55.160.20, UDP_-_NOEDNS_)
- lkpp.go.id/NS: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, UDP_-_NOEDNS_)
- lkpp.go.id/SOA: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, TCP_-_NOEDNS_)
- lkpp.go.id/SOA: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- lkpp.go.id/TXT: The response had an invalid RCODE (SERVFAIL). (103.55.160.78, UDP_-_NOEDNS_)
Warnings (15)
- RRSIG NSEC proving non-existence of lkpp.go.id/DS alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/SOA alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- go.id to lkpp.go.id: The glue address(es) for ns2.lkpp.go.id (103.55.160.20) differed from its authoritative address(es) (103.55.160.78).
- go.id/DS (alg 10, id 48051): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- go.id/DS (alg 10, id 48051): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
- id/DS (alg 8, id 26887): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- id/DS (alg 8, id 26887): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
JavaScript is required to make the graph below interactive.
