View on GitHub

DNSViz: A DNS visualization tool

infotek.net.id

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • infotek.net.id/A
  • infotek.net.id/MX
  • infotek.net.id/NS
  • infotek.net.id/NSEC3PARAM
  • infotek.net.id/SOA
  • infotek.net.id/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • id/DNSKEY (alg 8, id 22449)
  • id/DNSKEY (alg 8, id 26887)
  • id/DS (alg 8, id 26887)
  • infotek.net.id/DNSKEY (alg 7, id 24293)
  • infotek.net.id/DNSKEY (alg 7, id 9123)
  • infotek.net.id/DS (alg 7, id 9123)
  • net.id/DNSKEY (alg 10, id 21768)
  • net.id/DNSKEY (alg 10, id 7070)
  • net.id/DS (alg 10, id 21768)

Delegation statusDelegation status

Secure (3)
  • . to id
  • id to net.id
  • net.id to infotek.net.id

NoticesNotices

Errors (21)
  • id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:d::d)
  • infotek.net.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.129.221.64, 103.140.54.101)
  • infotek.net.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.129.221.64, 103.140.54.101)
  • infotek.net.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.206.169.40, 103.206.169.131, 103.206.169.137, 103.206.169.233)
  • infotek.net.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.206.169.40, 103.206.169.131, 103.206.169.137, 103.206.169.233, UDP_-_NOEDNS_)
  • infotek.net.id/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_NOEDNS_)
  • infotek.net.id/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • infotek.net.id/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • infotek.net.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.206.169.40, 103.206.169.131, 103.206.169.137, 103.206.169.233, UDP_-_NOEDNS_)
  • infotek.net.id/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_NOEDNS_)
  • infotek.net.id/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_NOEDNS_)
  • infotek.net.id/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, TCP_-_NOEDNS_)
  • infotek.net.id/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • infotek.net.id/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.129.221.64, 103.140.54.101, UDP_-_NOEDNS_)
  • net.id zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (45.126.57.57)
  • net.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:d::d)
  • net.id/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (45.126.57.57, TCP_-_EDNS0_4096_D_KN)
  • infotek.net.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 2956tqc7i0.infotek.net.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
  • RRSIG infotek.net.id/A alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/DNSKEY alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/DNSKEY alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/DNSKEY alg 7, id 9123: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/DNSKEY alg 7, id 9123: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/DS alg 10, id 7070: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/MX alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/NS alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/NSEC3PARAM alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/SOA alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG infotek.net.id/TXT alg 7, id 24293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG net.id/DNSKEY alg 10, id 21768: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG net.id/DNSKEY alg 10, id 21768: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG net.id/DNSKEY alg 10, id 7070: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG net.id/DNSKEY alg 10, id 7070: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • infotek.net.id/DS (alg 7, id 9123): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • infotek.net.id/DS (alg 7, id 9123): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • infotek.net.id/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2956tqc7i0.infotek.net.id/A 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