netapp.com
Updated:
2021-10-22 16:56:32 UTC (1128 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- netapp.com/A
- netapp.com/MX
- netapp.com/NS
- netapp.com/SOA
- netapp.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of netapp.com/DS
- com/DNSKEY (alg 8, id 15549)
- com/DNSKEY (alg 8, id 30909)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to netapp.com
Secure (1)
- . to com
Notices
Errors (3)
- netapp.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (202.3.124.28, 217.70.210.19)
- netapp.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.3.124.28, 217.70.210.19, UDP_-_NOEDNS_)
- netapp.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.3.124.28, 217.70.210.19, UDP_-_NOEDNS_)
Warnings (2)
- com to netapp.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): vmacsiapp40-prd.netapp.com See RFC 1034, Sec. 4.2.2.
- com to netapp.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns040.netapp.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
