adp.com
Updated:
2020-11-16 02:19:37 UTC (1470 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- adp.com/A
- adp.com/MX
- adp.com/NS
- adp.com/SOA
- adp.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of adp.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 31510)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to adp.com
Secure (1)
- . to com
Notices
Errors (3)
- adp.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2605:4580:3001::)
- adp.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2605:4580:3001::, UDP_-_NOEDNS_)
- adp.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2605:4580:3001::, UDP_-_NOEDNS_)
Warnings (1)
- com to adp.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: a1-199.akam.net, a14-65.akam.net, a18-66.akam.net, a28-64.akam.net, a5-66.akam.net, a9-67.akam.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
