zendesk.com
Updated:
2024-08-07 02:16:44 UTC (136 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- zendesk.com/A
- zendesk.com/MX
- zendesk.com/NS
- zendesk.com/SOA
- zendesk.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of zendesk.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 59354)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to zendesk.com
Secure (1)
- . to com
Notices
Warnings (5)
- ./DNSKEY: 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_512_D_KN)
- com to zendesk.com: Authoritative AAAA records exist for ns-444.awsdns-55.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com/DS (alg 13, id 19718): 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)
- com/DS (alg 13, id 19718): 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)
- zendesk.com/TXT: 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. (2600:9000:5301:bc00::1, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
