infotek.net.id
Updated:
2025-01-20 08:46:45 UTC (335 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset 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 status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26470)
- ./DNSKEY (alg 8, id 38696)
- 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 status
Secure (3)
- . to id
- id to net.id
- net.id to infotek.net.id
Notices
Errors (12)
- 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) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.206.169.131, 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.131, 103.206.169.233, 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.131, 103.206.169.233, UDP_-_NOEDNS_)
- net.id zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4)
- 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 UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, UDP_-_EDNS0_4096_D_KN)
- infotek.net.id/CNAME 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.
- t4jl1.zrhmt.infotek.net.id/A 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/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
- 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.
- 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): pns34.cloudns.net See RFC 1034, Sec. 4.2.2.
- t4jl1.zrhmt.infotek.net.id/A 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/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.
JavaScript is required to make the graph below interactive.
