View on GitHub
cognizant.com
Updated:
2024-06-27 10:03:59 UTC
(
72 days ago
)
Update now
« 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
(5)
cognizant.com/A
cognizant.com/MX
cognizant.com/NS
cognizant.com/SOA
cognizant.com/TXT
Secure
(2)
com/SOA
com/SOA
DNSKEY/DS/NSEC status
Secure
(7)
./DNSKEY (alg 8, id 20038)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 5613)
NSEC3 proving non-existence of cognizant.com/DS
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 956)
com/DS (alg 13, id 19718)
Delegation status
Insecure
(1)
com to cognizant.com
Secure
(1)
. to com
Notices
Errors
(3)
cognizant.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (20.44.34.11)
cognizant.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (20.44.34.11, TCP_-_EDNS0_4096_D_N)
cognizant.com/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (20.44.34.11, TCP_-_EDNS0_4096_D_KN)
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.