View on GitHub

DNSViz: A DNS visualization tool

ic3.gov

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

RRset statusRRset status

Secure (7)
  • ic3.gov/A
  • ic3.gov/AAAA
  • ic3.gov/MX
  • ic3.gov/NS
  • ic3.gov/NSEC3PARAM
  • ic3.gov/SOA
  • ic3.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
  • ic3.gov/DNSKEY (alg 13, id 34754)
  • ic3.gov/DNSKEY (alg 8, id 31369)
  • ic3.gov/DNSKEY (alg 8, id 6781)
  • ic3.gov/DS (alg 8, id 31369)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to ic3.gov

NoticesNotices

Errors (15)
  • ic3.gov/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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/DNSKEY (alg 13, id 34754): 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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/DNSKEY (alg 8, id 31369): 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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/DNSKEY (alg 8, id 6781): 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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ic3.gov/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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/NSEC3PARAM: 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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ic3.gov/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. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • glcjp.i0wor.ic3.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ic3.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ic3.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • ic3.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • ic3.gov/MX: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/NS: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (20.141.170.64, 52.126.48.246, 2001:489a:3102:6::62, 2001:489a:3600::13, UDP_-_EDNS0_4096_D_KN)
  • ic3.gov/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ic3.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ic3.gov/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