View on GitHub

DNSViz: A DNS visualization tool

4gjn.com

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

RRset statusRRset status

Bogus (2)
  • 4gjn.com/SOA
  • 4gjn.com/TXT (NODATA)
Secure (6)
  • 4gjn.com/A
  • 4gjn.com/AAAA
  • 4gjn.com/MX
  • 4gjn.com/NS
  • 4gjn.com/SOA
  • 4gjn.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (3)
  • 4gjn.com/DNSKEY (alg 8, id 3991)
  • 4gjn.com/DNSKEY (alg 8, id 4713)
  • NSEC3 proving non-existence of 4gjn.com/TXT
Secure (10)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • 4gjn.com/DNSKEY (alg 13, id 21691)
  • 4gjn.com/DNSKEY (alg 13, id 4558)
  • 4gjn.com/DS (alg 13, id 4548)
  • 4gjn.com/DS (alg 13, id 4558)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 54714)
  • com/DS (alg 8, id 30909)
Non_existent (1)
  • 4gjn.com/DNSKEY (alg 13, id 4548)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to 4gjn.com

NoticesNotices

Errors (41)
  • 4gjn.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a02:16a8:dc:400::211)
  • 4gjn.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2a02:16a8:dc:400::211, UDP_-_NOEDNS_)
  • 4gjn.com/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/A: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/AAAA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/AAAA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/AAAA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/DNSKEY (alg 13, id 21691): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • 4gjn.com/DNSKEY (alg 13, id 21691): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 4gjn.com/DNSKEY (alg 13, id 4558): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • 4gjn.com/DNSKEY (alg 13, id 4558): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 4gjn.com/DNSKEY (alg 8, id 3991): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • 4gjn.com/DNSKEY (alg 8, id 3991): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • 4gjn.com/DNSKEY (alg 8, id 4713): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 4gjn.com/DNSKEY (alg 8, id 4713): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • 4gjn.com/DNSKEY (alg 8, id 4713): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • 4gjn.com/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 4gjn.com/MX: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 4gjn.com/MX: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 4gjn.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2a02:16a8:dc:400::211, UDP_-_NOEDNS_)
  • 4gjn.com/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/NS: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 4gjn.com/SOA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • 4gjn.com/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of 4gjn.com/TXT: 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 4gjn.com/TXT: 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 4gjn.com/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of 4gjn.com/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of 4gjn.com/TXT: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of 4gjn.com/TXT: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of 4gjn.com/TXT: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: 4gjn.com/TXT See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of 4gjn.com/TXT: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: 4gjn.com/TXT See RFC 5155, Sec. 8.5.
  • com to 4gjn.com: 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. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • com to 4gjn.com: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (217.61.111.93, TCP_-_EDNS0_4096_D_KN)
  • cln89igyo0.4gjn.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 4gjn.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 4gjn.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • 4gjn.com/DNSKEY (alg 8, id 3991): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (89.26.108.11, 217.196.154.211, 2001:470:1f0b:371::221, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • NSEC3 proving non-existence of 4gjn.com/TXT: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of 4gjn.com/TXT: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • cln89igyo0.4gjn.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 4gjn.com/CNAME 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