lilly.com
Updated:
2023-03-20 03:53:50 UTC (613 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- lilly.com/A
- lilly.com/AAAA
- lilly.com/AAAA
- lilly.com/MX
- lilly.com/NS
- lilly.com/SOA
- lilly.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 lilly.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 lilly.com
Secure (1)
- . to com
Notices
Errors (5)
- lilly.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:1401:2::21, UDP_-_NOEDNS_)
- lilly.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2600:1401:2::21, UDP_-_EDNS0_512_D_KN)
- lilly.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2600:1401:2::21, UDP_-_EDNS0_512_D_KN)
- lilly.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2600:1401:2::21, TCP_-_EDNS0_4096_D_N)
- lilly.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- lilly.com/SOA: 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:1401:2::21, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- lilly.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- lilly.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- lilly.com/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
