View on GitHub

DNSViz: A DNS visualization tool

etisalat.eg

Updated: 2020-07-08 05:08:05 UTC (1998 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • eg/SOA
  • etisalat.eg/A
  • etisalat.eg/MX
  • etisalat.eg/NS
  • etisalat.eg/SOA
  • etisalat.eg/TXT
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

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

NoticesNotices

Errors (13)
  • etisalat.eg zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227)
  • etisalat.eg zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227)
  • etisalat.eg/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, UDP_-_EDNS0_4096_D_K)
  • etisalat.eg/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • etisalat.eg/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • etisalat.eg/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, UDP_-_EDNS0_4096_D_K)
  • etisalat.eg/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, TCP_-_EDNS0_4096_D)
  • etisalat.eg/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • etisalat.eg/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (91.192.40.21, 176.9.224.227, 195.140.184.21, 2a01:4f8:150:5017::227, UDP_-_EDNS0_4096_D_K)
  • dharn7lzwt.etisalat.eg/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • etisalat.eg/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • etisalat.eg/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • etisalat.eg/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • eg to etisalat.eg: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the eg zone): ns1.ecircle.de, ns2.ecircle.de, ns3.ecircle.com See RFC 1034, Sec. 4.2.2.

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