livenation.com
Updated:
2022-08-25 15:14:25 UTC (909 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- livenation.com/A
- livenation.com/MX
- livenation.com/NS
- livenation.com/SOA
- livenation.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of livenation.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 32298)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to livenation.com
Secure (1)
- . to com
Notices
Errors (2)
- livenation.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2600:1406:32::40, UDP_-_EDNS0_512_D_KN)
- livenation.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- com to livenation.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): a4-67.akam.net, a18-65.akam.net, a7-64.akam.net, a20-66.akam.net See RFC 1034, Sec. 4.2.2.
- livenation.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:1406:32::40, UDP_-_EDNS0_4096_D_KN_0x20)
- livenation.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:1406:32::40, UDP_-_EDNS0_4096_D_KN)
- ur704asjp9.livenation.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- livenation.com/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
