View on GitHub

DNSViz: A DNS visualization tool

lb

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

RRset statusRRset status

Bogus (1)
  • lb/SOA
Secure (2)
  • lb/NS
  • lb/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • lb/DNSKEY (alg 8, id 25074)
  • lb/DNSKEY (alg 8, id 31165)
  • lb/DNSKEY (alg 8, id 3842)
  • lb/DS (alg 8, id 3842)

Delegation statusDelegation status

Secure (1)
  • . to lb

NoticesNotices

Errors (22)
  • . to lb: 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. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • . to lb: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • RRSIG lb/DNSKEY alg 8, id 3842: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 15 hours, 14 minutes after it expires at 2024-06-11 20:17:51+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG lb/DNSKEY alg 8, id 3842: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 15 hours, 14 minutes after it expires at 2024-06-11 20:17:51+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG lb/DNSKEY alg 8, id 3842: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 15 hours, 14 minutes after it expires at 2024-06-11 20:17:51+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG lb/NS alg 8, id 25074: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-06-11 20:17:51+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG lb/NS alg 8, id 31165: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-06-11 20:17:51+00:00. See RFC 4035, Sec. 5.3.3.
  • lb zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (78.141.235.25)
  • lb zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (147.28.0.39, 2001:418:1::39)
  • lb/DNSKEY (alg 8, id 25074): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • lb/DNSKEY (alg 8, id 31165): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • lb/DNSKEY (alg 8, id 3842): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • lb/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, UDP_-_EDNS0_4096_D_KN)
  • lb/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (147.28.0.39, 2001:418:1::39, UDP_-_NOEDNS_)
  • lb/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (77.72.229.254, 105.16.115.1, 105.16.170.1, 139.84.235.208, 158.38.0.181, 185.91.97.18, 203.178.141.64, 2001:200:0:2::53:1, 2001:700:0:503::aa:5302, 2a01:3f0:0:306::53, 2a05:e380:2:4::2, 2a05:f480:3000:205f:5400:4ff:fea4:e565, 2c0f:feb0:2:1::1:8001, 2c0f:feb0:c:1::1:1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • lb/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (78.141.235.25, TCP_-_EDNS0_4096_D_N)
  • lb/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • wfxld.w5xej.lb/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • lb/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • lb/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • lb/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • lb/CDS has errors; 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