View on GitHub

DNSViz: A DNS visualization tool

sp.edu.sg

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

RRset statusRRset status

Insecure (6)
  • sp.edu.sg/A
  • sp.edu.sg/AAAA
  • sp.edu.sg/MX
  • sp.edu.sg/NS
  • sp.edu.sg/SOA
  • sp.edu.sg/TXT
Secure (1)
  • edu.sg/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • sp.edu.sg/DNSKEY (alg 13, id 5015)
  • sp.edu.sg/DNSKEY (alg 13, id 56518)
  • sp.edu.sg/DNSKEY (alg 13, id 57603)
Secure (12)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of sp.edu.sg/DS
  • edu.sg/DNSKEY (alg 8, id 10130)
  • edu.sg/DNSKEY (alg 8, id 36969)
  • edu.sg/DNSKEY (alg 8, id 5031)
  • edu.sg/DS (alg 8, id 10130)
  • sg/DNSKEY (alg 8, id 27933)
  • sg/DNSKEY (alg 8, id 27954)
  • sg/DNSKEY (alg 8, id 46664)
  • sg/DS (alg 8, id 46664)

Delegation statusDelegation status

Insecure (1)
  • edu.sg to sp.edu.sg
Secure (2)
  • . to sg
  • sg to edu.sg

NoticesNotices

Errors (16)
  • NSEC3 proving non-existence of sp.edu.sg/DS: 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 sp.edu.sg/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • sp.edu.sg/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN)
  • sp.edu.sg/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN)
  • sp.edu.sg/DNSKEY (alg 13, id 5015): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sp.edu.sg/DNSKEY (alg 13, id 56518): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sp.edu.sg/DNSKEY (alg 13, id 57603): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sp.edu.sg/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sp.edu.sg/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN)
  • sp.edu.sg/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sp.edu.sg/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.154, 205.251.195.239, 205.251.196.214, 205.251.199.54, 2600:9000:5300:9a00::1, 2600:9000:5303:ef00::1, 2600:9000:5304:d600::1, 2600:9000:5307:3600::1, UDP_-_EDNS0_4096_D_KN)
  • sp.edu.sg/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ar3qo74db1.sp.edu.sg/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sp.edu.sg/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • sp.edu.sg/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • sp.edu.sg/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of sp.edu.sg/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sp.edu.sg/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • sp.edu.sg/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