gov.eg
Updated:
2024-08-29 12:26:29 UTC (128 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- eg/SOA
- gov.eg/NS
- gov.eg/SOA
Secure (1)
- ./SOA
DNSKEY/DS/NSEC status
Secure (3)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC proving non-existence of eg/DS
Delegation status
Insecure (2)
- . to eg
- eg to gov.eg
Notices
Errors (3)
- gov.eg zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (163.121.2.2)
- gov.eg/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (163.121.2.2, UDP_-_NOEDNS_)
- gov.eg/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- . to eg: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- eg to gov.eg: The following NS name(s) were found in the delegation NS RRset (i.e., in the eg zone), but not in the authoritative NS RRset: ns.idsc.gov.eg See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
