amgen.com
Updated:
2024-08-29 00:58:58 UTC (84 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- amgen.com/A
- amgen.com/MX
- amgen.com/NS
- amgen.com/SOA
- amgen.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 amgen.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 amgen.com
Secure (1)
- . to com
Notices
Errors (3)
- amgen.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (138.133.60.24)
- amgen.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (138.133.60.24, UDP_-_NOEDNS_)
- amgen.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (138.133.60.24, UDP_-_NOEDNS_)
Warnings (3)
- ./DNSKEY (alg 8, id 20038): 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)
- ./DNSKEY (alg 8, id 20326): 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 to amgen.com: The glue address(es) for ns2.amgen.com (138.133.60.24) differed from its authoritative address(es) (138.133.61.100). See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
