View on GitHub
gov.ao
Updated:
2021-10-22 15:28:27 UTC
(
1174 days ago
)
Go to most recent »
« Previous analysis
|
Next analysis »
Tweet
DNSSEC
Responses
Servers
Analyze
DNSSEC options (
hide
)
|?|
RR types:
--All--
A
AAAA
TXT
PTR
MX
NS
SOA
CNAME
SRV
NAPTR
TLSA
NSEC3PARAM
CDNSKEY
CDS
CAA
|?|
DNSSEC algorithms:
--All--
1 - RSA/MD5
3 - DSA/SHA1
5 - RSA/SHA-1
6 - DSA-NSEC3-SHA1
7 - RSASHA1-NSEC3-SHA1
8 - RSA/SHA-256
10 - RSA/SHA-512
12 - GOST R 34.10-2001
13 - ECDSA Curve P-256 with SHA-256
14 - ECDSA Curve P-384 with SHA-384
15 - Ed25519
16 - Ed448
|?|
DS digest algorithms:
--All--
1 - SHA-1
2 - SHA-256
3 - GOST R 34.11-94
4 - SHA-384
|?|
Denial of existence:
|?|
Redundant edges:
|?|
Ignore RFC 8624:
|?|
Ignore RFC 9276:
|?|
Multi-signer:
|?|
Trust anchors:
Root zone KSK
|?|
Additional trusted keys:
Notices
DNSSEC Authentication Chain
RRset status
Insecure
(1)
ao/SOA
Secure
(1)
./SOA
DNSKEY/DS/NSEC status
Secure
(3)
./DNSKEY (alg 8, id 14748)
./DNSKEY (alg 8, id 20326)
NSEC proving non-existence of ao/DS
Delegation status
Lame
(1)
ao to gov.ao
Insecure
(1)
. to ao
Notices
Errors
(18)
gov.ao zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.222.202.35)
gov.ao zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.222.202.35)
gov.ao zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (154.116.255.21, 154.116.255.22)
gov.ao zone: There was an error resolving the following NS name(s) to address(es): ns1.gov.ao, ns2.gov.ao, ns4.gov.ao
gov.ao/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (154.116.255.21, 154.116.255.22, UDP_-_NOEDNS_)
gov.ao/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_NOEDNS_)
gov.ao/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_NOEDNS_)
gov.ao/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
gov.ao/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
gov.ao/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (154.116.255.21, 154.116.255.22, UDP_-_NOEDNS_)
gov.ao/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_NOEDNS_)
gov.ao/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_NOEDNS_)
gov.ao/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, TCP_-_NOEDNS_)
gov.ao/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
gov.ao/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.222.202.35, UDP_-_NOEDNS_)
gov.ao/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
u1x2jg47ds.gov.ao/A has errors; select the "Denial of existence" DNSSEC option to see them.
gov.ao/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
DNSKEY legend
Full legend
SEP bit set
Revoke bit set
Trust anchor
See also
DNSSEC Debugger
by
Verisign Labs
.
Download:
png
|
svg
JavaScript is required to make the graph below interactive.