View on GitHub
amgen.com
Updated:
2023-01-17 16:52:58 UTC
(
138 days ago
)
Update now
« Previous analysis
|
Next analysis »
Tweet
DNSSEC
Responses
Servers
Analyze
DNSSEC options (
hide
)
|?|
RR types:
--All--
A
AAAA
TXT
PTR
MX
NS
SOA
CNAME
SRV
NAPTR
TLSA
NSEC3PARAM
CAA
|?|
DNSSEC algorithms:
--All--
1 - RSA/MD5
3 - DSA/SHA1
5 - RSA/SHA-1
6 - DSA-NSEC3-SHA1
7 - RSASHA1-NSEC3-SHA1
8 - RSA/SHA-256
10 - RSA/SHA-512
12 - GOST R 34.10-2001
13 - ECDSA Curve P-256 with SHA-256
14 - ECDSA Curve P-384 with SHA-384
15 - Ed25519
16 - Ed448
|?|
DS digest algorithms:
--All--
1 - SHA-1
2 - SHA-256
3 - GOST R 34.11-94
4 - SHA-384
|?|
Denial of existence:
|?|
Redundant edges:
|?|
Trust anchors:
Root zone KSK
|?|
Additional trusted keys:
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
(7)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 951)
NSEC3 proving non-existence of amgen.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 36739)
com/DNSKEY (alg 8, id 53929)
com/DS (alg 8, id 30909)
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. (138.133.60.24)
amgen.com/A: No response was received from the server over UDP (tried 12 times). (138.133.60.24, UDP_-_NOEDNS_)
amgen.com/NS: No response was received from the server over UDP (tried 12 times). (138.133.60.24, UDP_-_NOEDNS_)
Warnings
(1)
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).
DNSKEY legend
Full legend
SEP bit set
Revoke bit set
Trust anchor
See also
DNSSEC Debugger
by
Verisign Labs
.
Download:
png
|
svg
JavaScript is required to make the graph below interactive.