cognizant.com
Updated:
2020-04-19 23:19:39 UTC (1524 days ago)
Go to most recent »
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 20326)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of cognizant.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 39844)
- com/DNSKEY (alg 8, id 56311)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to cognizant.com
Secure (1)
- . to com
Notices
Errors (2)
- 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)
Warnings (2)
- com/DS (alg 8, id 30909): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
- com/DS (alg 8, id 30909): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
JavaScript is required to make the graph below interactive.
