View on GitHub

DNSViz: A DNS visualization tool

sauditelecom.com.sa

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

RRset statusRRset status

Bogus (4)
  • sauditelecom.com.sa/A
  • sauditelecom.com.sa/MX
  • sauditelecom.com.sa/NS
  • sauditelecom.com.sa/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • sauditelecom.com.sa/DNSKEY (alg 5, id 26164)
  • sauditelecom.com.sa/DNSKEY (alg 5, id 46092)
  • sauditelecom.com.sa/DNSKEY (alg 5, id 52470)
  • sauditelecom.com.sa/DNSKEY (alg 5, id 61155)
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • com.sa/DNSKEY (alg 8, id 32584)
  • com.sa/DNSKEY (alg 8, id 48156)
  • com.sa/DS (alg 8, id 32584)
  • sa/DNSKEY (alg 8, id 30574)
  • sa/DNSKEY (alg 8, id 59283)
  • sa/DS (alg 8, id 30574)
  • sauditelecom.com.sa/DS (alg 5, id 376)
Non_existent (1)
  • sauditelecom.com.sa/DNSKEY (alg 5, id 376)

Delegation statusDelegation status

Bogus (1)
  • com.sa to sauditelecom.com.sa
Secure (2)
  • . to sa
  • sa to com.sa

NoticesNotices

Errors (4)
  • com.sa to sauditelecom.com.sa: 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. (94.97.1.31, 94.97.1.32, 2001:16a0:6000:4000:1::11, 2001:16a0:6000:4000:1::14, UDP_-_EDNS0_4096_D_K)
  • com.sa to sauditelecom.com.sa: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (94.97.1.31, 94.97.1.32, 2001:16a0:6000:4000:1::11, 2001:16a0:6000:4000:1::14, UDP_-_EDNS0_4096_D_K)
  • com.sa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:1490:0:800::118)
  • sa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:1490:0:800::118)
Warnings (17)
  • RRSIG sauditelecom.com.sa/A alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 26164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 26164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 26164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 26164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/DNSKEY alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/MX alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/NS alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sauditelecom.com.sa/SOA alg 5, id 61155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • sauditelecom.com.sa/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sauditelecom.com.sa/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • g42icz0t6b.sauditelecom.com.sa/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sauditelecom.com.sa/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sauditelecom.com.sa/TXT 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