itt.com
Updated:
2023-01-24 13:22:30 UTC (679 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- itt.com/A
- itt.com/MX
- itt.com/NS
- itt.com/SOA
- itt.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of itt.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 36739)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to itt.com
Secure (1)
- . to com
Notices
Errors (2)
- itt.com/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (108.59.161.5, 108.59.162.5, 108.59.163.5, 108.59.164.5, 2600:2000:2210::5, 2600:2000:2220::5, 2600:2000:2230::5, 2600:2000:2240::5, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- itt.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 951): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
