dynect.net
Updated:
2022-02-11 00:47:50 UTC (1048 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- dynect.net/A
- dynect.net/AAAA
- dynect.net/MX
- dynect.net/NS
- dynect.net/SOA
- dynect.net/TXT
Secure (2)
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of dynect.net/DS
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 4604)
- net/DS (alg 8, id 35886)
Delegation status
Insecure (1)
- net to dynect.net
Secure (1)
- . to net
Notices
Errors (4)
- dynect.net zone: The following NS name(s) did not resolve to address(es): ns7.dynamicnetworkservices.net
- dynect.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (108.59.165.1, 2a02:e180:8::1)
- dynect.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (108.59.165.1, 2a02:e180:8::1, UDP_-_NOEDNS_)
- dynect.net/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (108.59.165.1, 2a02:e180:8::1, UDP_-_NOEDNS_)
Warnings (1)
- net to dynect.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns7.dynamicnetworkservices.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
