View on GitHub

DNSViz: A DNS visualization tool

lkpp.go.id

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset 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 statusDNSKEY/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 statusDelegation status

Insecure (1)
  • go.id to lkpp.go.id
Secure (2)
  • . to id
  • id to go.id

NoticesNotices

Errors (20)
  • go.id/DS (alg 10, id 48051): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • go.id/DS (alg 10, id 48051): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • id/DS (alg 8, id 26887): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • id/DS (alg 8, id 26887): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • lkpp.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. (103.55.160.78)
  • lkpp.go.id zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (103.55.160.78)
  • lkpp.go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.55.160.20)
  • lkpp.go.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.55.160.20, UDP_-_NOEDNS_)
  • lkpp.go.id/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.55.160.78, UDP_-_NOEDNS_)
  • lkpp.go.id/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.55.160.78, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • lkpp.go.id/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (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). See RFC 1035, Sec. 4.2. (103.55.160.20, UDP_-_NOEDNS_)
  • lkpp.go.id/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.55.160.78, UDP_-_NOEDNS_)
  • lkpp.go.id/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.55.160.78, TCP_-_NOEDNS_)
  • lkpp.go.id/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.55.160.78, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • lkpp.go.id/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.55.160.78, UDP_-_NOEDNS_)
  • lkpp.go.id/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • lkpp.go.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • t4kmjfeayu.lkpp.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • lkpp.go.id/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • RRSIG NSEC proving non-existence of lkpp.go.id/DS alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/SOA alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • 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). See RFC 1034, Sec. 4.2.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): 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.
  • lkpp.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph