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

Bogus (8)
  • ./SOA
  • infotek.net.id/A
  • infotek.net.id/AAAA
  • infotek.net.id/MX
  • infotek.net.id/NS (NODATA)
  • infotek.net.id/NSEC3PARAM (NODATA)
  • infotek.net.id/SOA (NODATA)
  • infotek.net.id/TXT
Secure (7)
  • infotek.net.id/A
  • infotek.net.id/AAAA (NODATA)
  • 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 (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 53148)
  • NSEC3 proving non-existence of infotek.net.id/AAAA
  • 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 (30)
  • ./SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • NSEC3 proving non-existence of infotek.net.id/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of infotek.net.id/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of infotek.net.id/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: infotek.net.id/AAAA See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of infotek.net.id/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: infotek.net.id/AAAA See RFC 5155, Sec. 8.5.
  • id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, 2402:ee80:b::b, 2402:ee80:c::c)
  • infotek.net.id zone: The following NS name(s) resolved to IP address(es) in private IP address space: ns.infotek.net.id, ns2.infotek.net.id
  • infotek.net.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.129.223.190, 103.206.169.131, 103.206.169.233)
  • infotek.net.id/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • infotek.net.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.129.223.190, 103.206.169.131, 103.206.169.233, UDP_-_NOEDNS_)
  • infotek.net.id/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • infotek.net.id/DNSKEY (alg 7, id 24293): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • infotek.net.id/DNSKEY (alg 7, id 9123): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • infotek.net.id/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • infotek.net.id/NS (NODATA): An SOA RR with owner name (.) not matching the zone name (infotek.net.id) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • infotek.net.id/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • infotek.net.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.129.223.190, 103.206.169.131, 103.206.169.233, UDP_-_NOEDNS_)
  • infotek.net.id/NSEC3PARAM (NODATA): An SOA RR with owner name (.) not matching the zone name (infotek.net.id) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • infotek.net.id/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • infotek.net.id/SOA (NODATA): An SOA RR with owner name (.) not matching the zone name (infotek.net.id) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • infotek.net.id/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • infotek.net.id/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN)
  • net.id to infotek.net.id: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • net.id to infotek.net.id: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.136.96.66, 185.136.97.66, 185.136.98.66, 185.136.99.66, 2a06:fb00:1::1:66, 2a06:fb00:1::2:66, 2a06:fb00:1::3:66, 2a06:fb00:1::4:66, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • net.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, 2402:ee80:b::b, 2402:ee80:c::c)
  • infotek.net.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • aysgj.fpq9k.infotek.net.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/CDS 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.
Warnings (28)
  • NSEC3 proving non-existence of infotek.net.id/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of infotek.net.id/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of infotek.net.id/AAAA 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/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/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.
  • 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.
  • net.id to infotek.net.id: Authoritative AAAA records exist for ns2.infotek.net.id, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • net.id to infotek.net.id: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net.id zone): ns.infotek.net.id, pns34.cloudns.net See RFC 1034, Sec. 4.2.2.
  • net.id to infotek.net.id: The glue address(es) for ns2.infotek.net.id (103.129.223.190) differed from its authoritative address(es) (103.129.220.13). See RFC 1034, Sec. 4.2.2.
  • aysgj.fpq9k.infotek.net.id/A 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.
  • infotek.net.id/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • infotek.net.id/CDS 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.

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