View on GitHub

DNSViz: A DNS visualization tool

gov.eg

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

RRset statusRRset status

Insecure (5)
  • eg/SOA
  • gov.eg/NS
  • gov.eg/NS
  • gov.eg/SOA
  • gov.eg/SOA (NODATA)
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC proving non-existence of eg/DS

Delegation statusDelegation status

Insecure (2)
  • . to eg
  • eg to gov.eg

NoticesNotices

Errors (15)
  • gov.eg zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (163.121.2.2)
  • gov.eg zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (193.227.1.1)
  • gov.eg/DNSKEY: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (163.121.2.2, UDP_-_EDNS0_512_D_KN)
  • gov.eg/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (163.121.2.2, UDP_-_EDNS0_4096_D)
  • gov.eg/SOA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (163.121.2.2, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_0x20)
  • gov.eg/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (163.121.2.2, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_0x20)
  • gov.eg/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (193.227.1.1, TCP_-_EDNS0_4096_D_N)
  • gov.eg/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 238eh9ytva.gov.eg/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • gov.eg/NS: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (163.121.2.2, UDP_-_EDNS0_4096_D_KN)
  • gov.eg/SOA (NODATA): The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (163.121.2.2, TCP_-_EDNS0_4096_D_N)
  • gov.eg/SOA (NODATA): The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (163.121.2.2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.eg/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 238eh9ytva.gov.eg/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.eg/MX 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